Multiple Codebase configurations
long-term
T
Tan Cod
We'd like the ability to add multiple codebase configurations in a single pipeline. We want to run builds in parallel whille using separate codebase configurations but are running into issues where the both CI stages are using the same commitSha. Ideally codebase configurations should be set per CI stage instead of per pipeline.
Log In
N
Nofar Bluestein
marked this post as
long-term
N
Nofar Bluestein
Hey,
Today, the Codebase is intentionally configured at the pipeline level, so any CI stage that uses the automatic clone inherits the same repository and commit SHA. This ensures consistent, reproducible pipeline executions across stages.
If a stage needs to work with a different repository or revision, you can disable the automatic clone for that stage and add a Git Clone step within the stage with the desired repo/branch/commit.
We’ve captured your feedback about supporting codebase configuration per CI stage natively, as it could simplify multi-repo pipeline setups.
Regards,
Nofar Bluestein
Product manager, CI