Checking updates exist from upstream remotes

[den-rain]

There is a flag -u, --update (Check updates exist from upstream remotes) for install and create conan commands. So, please add an ability to set this flag when we use your tools. Thank you!

[danimtb]

Every time a new job starts, CPT install fresh requirements needed, so I am not sure if the --update flag makes sense here. Or maybe I am missing something. Could you please elaborate?

[lasote]

@danimtb it depends if they run the CPT in a fresh environment or not. It can be used (if not using docker) with a previously populated shared Conan cache. I was checking the readme and we have an "args" parameter to the ConanMultiPackager:

args: List with the parameters that will be passed to "conan test" command. e.j: args=['--build', 'all']. Default sys.argv[1:]

Unforntunately since now we are using the Conan python api it is not working anymore. We would need to add a new parameter somehow to indicate the --update and remove the old and useless args

[den-rain]

Yes, lasote is right, the flag is useful when we don't create a fresh environment for every build. More over, we have some policy for unstable packages in our team, so we periodically overwrite some unstable packages with the same version number in our conan server and we want to get this overwritten packages in our builds. We can do it only with --update flag.

[Johnnyxy]

Hi there, I have the same problem, that my CI build nodes do not clear the Conan cache before building. And now my build nodes are using old recipes which are not working anymore.

Has this been resolved in the meantime?

It looks like the args argument has been removed (like @lasote mentioned) but I did not find anything that is named update or something like that.

[danimtb]

I am tagging the issue so we can take the feature request into account. It makes sense to bring that capability back