Continuous deployment/delivery with Jenkins and VS Team Services
May 27, 2016Anand Gaurav

Summary
This post details how to integrate Jenkins CI pipelines with Azure DevOps Release Management for continuous deployment. It outlines the steps to set up a Jenkins project to archive build artifacts, create a Jenkins service endpoint in Azure DevOps, link the Jenkins build project as an artifact source in a Release Definition, and configure deployment steps. Additionally, it explains how to use the 'VS Team Services Continuous Deployment' Jenkins plugin to automatically trigger Azure DevOps releases upon completion of Jenkins builds, leveraging REST APIs and Personal Access Tokens (PATs) for authentication.
More from the Azure DevOps Pipelines for Dev-to-Prod Promotion trail
- Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
- Azure Developer CLI: From Dev to Prod with One Click
- February Patches for Azure DevOps Server
- Revolutionizing Requirement Gathering: Azure DevOps Meets Azure OpenAI using Semantic kernel
- Deploy a Java application to Azure App Service using GitHub Actions