Builds
The Builds page displays every pipeline build triggered by merges to your repository. Use this page to verify that builds completed, inspect which packages were produced, and trace builds to their resulting release candidates.
How builds appear
Builds are created automatically when a developer merges a pull request into the trunk branch. The pipeline builds only the packages affected by the merge. Each build row represents one pipeline execution.
codev does not trigger builds. It reads build data from sfp server and displays it in real time.
Table columns
COMMIT
Commit hash, message, author, and timestamp
a1b2c3d — "fix: update trigger handler" — John — 2 hours ago
DURATION
How long the build took
12m 34s
WINDMILL
Link to the pipeline execution details
Opens the flow run in your pipeline dashboard
RC
The release candidate name generated by this build (if any)
sales-RC-42
PACKAGE
The package that was built
core-triggers
VERSION
The artifact version published
1.5.0
DOMAIN
Which release domain this package belongs to
sales
STATUS
Current build status
Done, Building
ACTIONS
Available actions on the build row
View details
Build statuses
Building
The pipeline is currently running — packages are being built, tested, or published
Done
The pipeline completed. Packages have been published and a release candidate may have been generated
Relationship to release candidates
A build that successfully publishes packages and generates a release definition results in a new release candidate. The RC column in the builds table shows which RC was created.
If a build shows Done but the RC column is empty, the release definition generation step may have encountered an issue. Check the pipeline logs for details.
To act on the resulting release candidate (release, sandbox deploy, or patch), navigate to CI/CD > Release Candidates.
Related
Last updated