vsts-64

Azure DevOps

Common Questions

Azure DevOps is a cloud--based platform that let you plan your projects using Agile tools, manage code in git repositories, and deploy using CI/CD systems. 

vsts-64

Triggers

  • Build Completed

    Triggers when a build of the specified organization is marked as completed

  • Code Checked-in

    Triggers when a code is checked-in under the specified path

  • Code Pushed

    Triggers when a new code is pushed to the specified organization

  • Pull Request Created

    Triggers when a new pull request is created in the specified organization

  • Pull Request Merge Attempted

    Triggers when merging of new pull request with existing one is attempted in the specified organization

  • Pull Request Updated

    Triggers when an existing pull request is updated in the specified organization

  • Release Abandoned

    Triggers when release is abandoned of the specified organization

  • Release Created

    Triggers when an new release is create for the specified organization

  • Release Deployment Approval Completed

    Triggers when approval of deployment release is completed

  • Release Deployment Approval Pending

    Triggers when release deployment approval of the specified organization is pending

  • Release Deployment Completed

    Triggers when the release deployment of the specified organization is completed

  • Release Deployment Started

    Triggers when the release deployment of the specified organization is started

  • Work Item Commented On

    Triggers when a new comment is added to the specified work item

  • Work Item Created

    Triggers when a new work item is created in the specified organization

  • Work Item Deleted

    Triggers when an existing work item is deleted form the specified organization

  • Work Item Restored

    Triggers when an existing work item is restored

  • Work Item Updated

    Triggers when an existing work item is updated

Common Questions

To use Azure DevOps in your workflow, you will first need to connect it with Built.io Flow.

To do this, drag any Azure DevOps action listed under Azure DevOps Services service on the canvas. In case of configuring Azure DevOps triggers, double-click the Start icon on your canvas and select Azure DevOps service. Then click on the Add New option listed under the Authorize Azure DevOps field in the configuration window. Built.io Flow permission window opens listing the scopes you want to allow. Click ALLOW.

1.png

Once you click ALLOW, a window pops up asking you to login to Azure DevOps from your Microsoft account. Enter the username and password an login to your account. If you are already logged-in, then the authorization will be added automatically to Built.io Flow.

2.png

Enter this details in the respective fields of the the Add Connection window and click ADD. You can now see the added authorization under the Authorize Azure DevOps field. Once added, this authorization will be available in all Azure DevOps actions and triggers.