CloudBees Jenkins Platform

#Integrate Jenkins and create CI/CD pipelines for your Visual Studio Team Services Git repositories

The CloudBees Jenkins Platform is the proven, fully-featured, enterprise platform for implementing continuous delivery (CD) processes powered by Jenkins. The Visual Studio Team Services feature enables you to:

• Trigger Jenkins builds and workflows when pushing code to Visual Studio Team Services Git repositories.
• Leverage multi-branch capabilities for better per-branch visibility with unique jobs, history and notifications.
• Automatically create a branch and job when performing a pull request then delete the branch once the code is merged.

Install the CloudBees Jenkins Visual Studio Team Services Plugin

On your CloudBees Jenkins Platform master, navigate to the "Manage Jenkins/Manage Plugins" screen and install the "Visual Studio Team Services Plugin."

Note: this plugin is only available on CloudBees Jenkins Platform and not available on Jenkins "Open Source."

(Optional) Install Visual Studio Team Services Extension

Open https://marketplace.visualstudio.com/items/cloudbees.cloudbees-jenkins-platform-extension in your browser. Select Get it free to activate CloudBees extension on your Visual Studio Team Services Account.

Trigger Jenkins build when pushing code to Visual Studio Team Services Git

Trigger Jenkins builds and workflows when pushing code to Visual Studio Team Services Git repositories using a Web Hook.

If you installed CloudBees' Visual Studio Team Services extension

Create a Visual Studio Team Services Service Hook of type "CloudBees" and configure its URL to $JENKINS_URL/ where $JENKINS_URL is the base url of your Jenkins server. There's no need for authentication credentials.

If you didn't installed CloudBees' Visual Studio Team Services extension

Create a Visual Studio Team Services Service Hook of type "Web Hook" and configure its URL to $JENKINS_URL/vsts-webhook/ where $JENKINS_URL is the base url of your Jenkins server. There's no need for authentication credentials.

Then, in your Jenkins job configuration, navigate to the "Build Triggers" section and check "Build when a change is pushed to Visual Studio Team Services".

Use Jenkins Multi Branch Jobs for better branch and pull request visibility

Leverage multi-branch capabilities for better per branch and per pull request visibility with unique jobs, history and notifications.

Install the Jenkins Multibranch Workflow Plugin and Jenkins will automatically create per branch and per pull request jobs.

Use "Jenkinsfile" to define the build configuration with the source code

Multiple branches of a source code repository may require different build configurations. To solve this problem, the Multibranch Workflow plugin uses a job definition stored with the source code in a file named Jenkinfile located at the root of the repository.

The Jenkinsfile uses the standard Jenkins Workflow syntax. You just have to replace the source code checkout step (e.g. git 'https://github.com/my-org/my-repo.git') with a special step checkout scm.

Sample 'Jenkinsfile' for a Maven project

node {
  stage 'Build and Test'
  env.PATH = "${tool 'Maven 3'}/bin:${env.PATH}"
  checkout scm
  sh 'mvn clean package'
}

The Jenkins Multibranch Workflow plugin will index the git repository and create one build job per branch and per pull request containing a file Jenkinsfile.

Jobs created for pull requests are automatically deleted when the pull requests are closed.

Create a "Multibranch Workflow project"

On Visual Studio Team Services web portal, navigate to your user profile and create a Personal Access Token (see here).

In Jenkins, Navigate to the "Branch Sources" section of the configuration pages of your job and create credentials of type "username/password". Use your Visual Studio Team Services personal token as password and the username can be anything, we recommend to use the Visual Studio Team Services username for documentation purpose. Then select the desired repository.

Jenkins will automatically discover all the branches of your Git repository and the existing pull requests and create on "sub job" per branch and per pull request.