You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The conan remove command is missing an option to skip without returning an error if the package to be removed does not exist.
Background: It is really cumbersome to build an Azure pipeline that detects if a package exists and only runs the conan remove task if it does. If using a pool with numerous agents, we cannot be sure in which state the conan cache on every single agent is, so we need to clean the cache just to be sure. Adding continueOnError: true to the task only helps partially, as the pipeline run will show "completed with warnings" which does not reflect the actual outcome properly.
The text was updated successfully, but these errors were encountered:
The conan remove command is missing an option to skip without returning an error if the package to be removed does not exist.
$ conan remove zlib/1.4
Remove summary:
Local Cache
This works without failing, not sure what you mean (zlib/1.4 doesn't exist yet)
Background: It is really cumbersome to build an Azure pipeline that detects if a package exists and only runs the conan remove task if it does. If using a pool with numerous agents, we cannot be sure in which state the conan cache on every single agent is, so we need to clean the cache just to be sure.
It is not clear the background. Why would you remove a package if it exists? The whole purpose of using Conan is not having to rebuild something that already exists, this flow shouldn't be necessary in the first place.
The
conan remove
command is missing an option to skip without returning an error if the package to be removed does not exist.Background: It is really cumbersome to build an Azure pipeline that detects if a package exists and only runs the
conan remove
task if it does. If using a pool with numerous agents, we cannot be sure in which state the conan cache on every single agent is, so we need to clean the cache just to be sure. AddingcontinueOnError: true
to the task only helps partially, as the pipeline run will show "completed with warnings" which does not reflect the actual outcome properly.The text was updated successfully, but these errors were encountered: