Releasing into an environment

For this example, we’ll assume that there is already an ant task defined in your build that will take a binary and deploy it to your environment. A separate task will verify the install was successful. If it is not, a task will run to rollback the deployment. We will also assume that earlier in the pipeline there is a dist stage with a create-installers job that will have already created the binary for us to use.

• Add a new stage named UAT with a job named deploy
• Ensure the following task block is in the deploy job configuration

When you are ready to deploy something into the UAT environment…

• Find the check-in you want to deploy
• Click on the manual transition into the UAT stage

• When the deploy is successful, the stage will be green and the UAT environment will contain the selected check-in

• When the deploy fails for some reason, the stage will be red and the UAT environment will contain the original check-in

Manually deploy to production

• named production with a job named deploy
• Ensure that the production stage is manual

When you are ready to deploy something into the production environment…

• Navigate to the pipeline history page
• Find the check-in you want to deploy
• Click on the details link of the dist stage

• Download the installer binary in the artifacts tab

• Manually install the binary into production
• If there are issues, manually rollback to the last known good installation