Release triggers

TFS 2017 | TFS 2015

Release triggers are an automation tool to deploy your application. When the trigger conditions are met, the pipeline will deploy your artifacts to the environment/stages you already specified.

Continuous deployment triggers

Continuous deployment triggers allow you to create a release every time a new build artifact is available. Using the build branch filters you can trigger deployment for a specific target branch. A release will be triggered only if the Git push contains a commit on the specified branch. For example, selecting main will trigger a release for a Git push which contains one or more commits to the main branch. To trigger a release for any commit to branches under features/, enter features/*. To trigger a release for commits to all branches, enter *. Note that all specified filters will be OR'ed.

Scheduled release triggers

Scheduled release trigger allow you to create new releases at specific times.

Select the schedule icon under the Artifacts section. Toggle the Enabled/Disabled button and specify your release schedule. You can set up multiple schedules to trigger a release.

Stage triggers

Stage triggers allow you set up specific conditions to trigger deployment to a specific stage.

• Select trigger: Set the trigger that will start the deployment to this stage automatically. Select "Release" to deploy to the stage every time a new release is created. Use the "Stage" option to deploy after deployments to selected stages are successful. To allow only manual deployments, select "Manual".

• Artifacts filter: Select artifact condition(s) to trigger a new deployment. A release will be deployed to this stage only if all artifact conditions are met.

  

• Schedule: Trigger a new deployment to this stage at a specific time.

  

• Pull-request deployment: Enabling this will allow pull request based releases to be deployed to this stage. Keep it disabled if this is a critical or production stage.

  

• Pre-deployment approvals: Select the users who can approve or reject deployments to this stage. By default, all users must approve the deployment. If a group is added, one user in the group must approve the deployment. You can also specify the timeout (the maximum time that an approval is allowed to be pending before it is automatically rejected) and approval policies.

  

• Gates: Allow you to set up specific gates to evaluate before the deployment.

  

• Deployment queue settings: Allow you to configure actions when multiple releases are queued for deployment.