Skip to main content
Version: 4.x

Build Repository

Overview​

The build repository manages the build versions of standard deployments and separates building from releasing: one build can be used by several deploy requests, for example to verify it in the test environment first and then release exactly the same artifact to production without rebuilding.

Build repository

The list groups builds by application and shows the latest version, build time, builder and status; expand an application to see all of its builds.

New build​

Click New, choose the application and environment (a standard deploy configuration) and fill in:

New build

  • Version: a version label such as v1.2.0, unique per deploy configuration.
  • Branch / tag: choose Branch plus a Commit ID, or a Tag, to decide which code is built.
  • Remarks: optional.

The build starts immediately and runs the build stage of the deploy configuration (before / after checkout hooks and packaging). Click Log to follow the output.

Operations​

  • Build: building a finished version again overwrites its artifact; useful for retrying after a failure.
  • Log: the full build output.
  • Delete: remove the version and its artifact; versions referenced by deploy requests are cleaned up when the requests are deleted.

Relation to deploy requests​

  • Choosing a Build repository version in a deploy request reuses the artifact and skips the build stage.
  • Choosing a branch or tag in a deploy request creates the build automatically and builds it as part of the deploy.
  • Each deploy configuration keeps at most Versions build records; the rest are removed by the nightly clean-up.

Permissions​

The build repository permissions are under Roles / Feature permissions / Deployment / Build Repository (view builds, new version, run build, delete version) and are further limited by the deploy permissions of the role (environments and applications).