...
Promoting stages can be used to limit which users can finish a build process, however additional work can be done to ensure certain builds never reach certain stages. In the example above you have a Deploy stage that can only be executed by your lead developer. Lets say that you also want to limit which builds can reach the Deploy. For example, you should only ever deploy builds that were triggered by a release branch checkin. This scenario can be achieved by creating an If Action that checks if the current repository branch is NOT the release branch. If it is not the release branch then we run a Stop Action that ends the current build. These actions should be placed at the end of the stage that executes immediately before the Deploy stage. Stopping a build will end the build immediately and will be considered as a successfully completed build.
Tagging Builds
Continua Builds can be tagged with additional information that may be useful for your Continua users. Builds can be tagged by two different methods:
- Automatically tag builds: Builds can be tagged automatically in the build process with the Tag Build Action.
- Manually tag builds:
Only users with the Tag Builds permission can tag builds.
Pinning Builds
Every build in Continua can be viewed via the build's view. The builds view has the following simple format.
...