Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions for Effective Lockfile Based Workflow #615

Open
Narwhalrus opened this issue Feb 1, 2023 · 0 comments
Open

Suggestions for Effective Lockfile Based Workflow #615

Narwhalrus opened this issue Feb 1, 2023 · 0 comments

Comments

@Narwhalrus
Copy link

I've been using CPT as part of my CI pipelines for a few months now and upon reading the documentation on using lockfiles in CI began to wonder if CPT could be used to apply a similar flow for a build matrix.

Assuming I'm not overlooking some feature of CPT that makes this unnecessary, this would prevent depedency upload "race conditions" during CPT package generation.

I see that the ConanMultiPackager class has a lockfile member and constructor argument, but passing a base lockfile results in an error when calling conan create:

conans.errors.ConanException: Lockfiles with --base do not contain profile information, cannot be used. Create a full lockfile

This seems to be per design (conan-io/conan#8144)

Does it make sense to add the flow described in the above issue as an option in CPT?

eg.

conan lock create ... --lockfile-out partial.lock --base
# for each configuration
conan lock create .. --lockfile partial.lock --lockfile-out full.lock -pr <generated_profile>
conan create ... --lockfile full.lock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant