Skip to content
This repository was archived by the owner on Mar 13, 2026. It is now read-only.
This repository was archived by the owner on Mar 13, 2026. It is now read-only.

Suggestions for Effective Lockfile Based Workflow #615

@Narwhalrus

Description

@Narwhalrus

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions