TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Git CI Integration for Azure DevOps

6 posts · Oct 2011 – Jan 2021

What this trail covers

Azure Pipelines provides a comprehensive CI/CD solution for open-source projects, offering unlimited build minutes, 10 parallel pipelines for free, cross-platform build support (Linux, Windows, macOS), scheduled builds, publishing of test results in various formats, and build badges for project READMEs. This enables efficient maintenance, rapid validation of pull requests, and clear visibility into project health for contributors and users. This post introduces the capability for public projects to use Azure Pipelines for free, with unlimited build minutes and 10 parallel pipelines. It also details how to integrate Jenkins as a CI system with Azure DevOps Release Pipelines for CD, enabling end-to-end traceability, work item tracking, manual approvals, and deployment to various services. The integration involves installing the Team Foundation Server plugin on Jenkins and configuring a Jenkins artifact source in Azure DevOps.

All Microsoft trails
  1. Generate a GitHub Actions workflow with Visual Studio or the dotnet CLIIntroduces the `dotnet new workflow` command, a template for generating GitHub Actions workflow files for .NET projects. This command simplifies the initial setup of CI pipelines by creating a basic workflow to build and test the .NET application. It allows specifying the .NET SDK version and the triggering branch. This complements the existing Visual Studio feature for generating GitHub Actions workflows.
  2. Run your CI with Jenkins and CD with Azure DevOpsThis post details the integration of Jenkins as a CI system with Azure DevOps Release Pipelines for CD. It outlines the steps to install the Team Foundation Server plugin on Jenkins, configure a post-build action to trigger releases in Azure DevOps, and set up a Jenkins service connection in Azure DevOps to consume Jenkins jobs as artifacts in release pipelines. This enables end-to-end traceability, work item tracking, manual approvals, and deployment to various services.
  3. Get the most out of your PRs with Branch PoliciesThis post introduces and details the configuration of branch policies for Git pull requests in Azure DevOps. It covers requiring a minimum number of peer reviews, specifying reviewers for particular file paths or types, and automatically building pull requests before they can be merged. It also explains different strategies for handling build updates when the target branch changes and the option for auto-completing pull requests once all policies are satisfied.
  4. Visual Studio Team Services and Team Foundation Server Java Capabilities Presentation and Demonstration Now Available at java.visualstudio.comThis post details the integration of Java applications with Azure VMs and AWS Elastic Beanstalk within Azure DevOps CI/CD pipelines. It showcases an AngularJS/JavaScript/Java web application ('DeepSpace') running on both Azure VM (Ubuntu Linux) and AWS Elastic Beanstalk (Amazon Linux) with Tomcat. Key features demonstrated include Application Insights instrumentation for metrics and events, Service Hooks integration with a third-party app, SSH connection to a Team Services Git repo, work item usage (Kanban, stories, tasks, bugs), Java contextual searching, IntelliJ IDEA plugin integration (clone, branch, commit with work item association, pull request) using REST APIs, automated Windows builds with Java 1.7 and Maven (triggered by PR, executing JUnit and JaCoCo), automated Azure Linux VM builds with CI/CD vNext agent using Java 1.7 and Gradle (executing PMD and CheckStyle), automated release deployments (CD) of Java WAR files to Azure Linux VMs ('Test/QA' and 'Production') with Selenium tests and AI deployment markers, and automated release deployments to an AWS Elastic Beanstalk VM running Tomcat 7 Java 7.
  5. Getting Started with Selenium Testing in a Continuous Integration Pipeline with Visual StudioThis post provides a detailed walkthrough of integrating Selenium UI tests into a Continuous Integration (CI) pipeline using Visual Studio Team Services (VSTS). It covers adding a new Unit Test project, installing necessary Selenium NuGet packages (webdriver, phantomJS, chromedriver, iedriver), authoring Selenium tests with C# code, and configuring build definitions to execute these tests. Specific challenges and solutions are addressed, including IE security setup, PhantomJS JSON errors, and the failure of interactive tests (like Firefox) on hosted build agents, recommending the use of PhantomJS or Selenium Grid for such scenarios. The post also details how to pass build parameters like URL and browser type to the tests and how to interpret test results within the build summary.
  7. Release Candidate of Visual Studio 2012 Update 3 now availableIntroduced a new source settings dialog in the build definition wizard to enable continuous integration for Git repositories, allowing selection of a specific branch for builds. Also added functionality to the Team Foundation Server 2012 upgrade wizard to preserve build settings from the previous installation.
  8. Run CI builds in your Git team projectThis post details how to configure continuous integration (CI) builds for Git team projects in Azure DevOps. It explains how to set up a team project, define the CI build process by specifying triggered branches and the solution to build, and how to initiate a build after committing and pushing code. It also includes a Q&A section addressing specific user queries about test runs, build customization, branch handling, retention policies, default branches, and work item association.
  9. Building iOS Apps in TFSThis post details how to set up a CI/CD pipeline for building iOS applications using Jenkins and Team Foundation Server (TFS). It outlines the necessary tools (TFS, Git-Tf, Jenkins, TEE CLC, Xcode, Git) and their roles in the workflow. The post explains the process of configuring TFS with alternate credentials for Git-Tf, enabling Git source control in Xcode projects, configuring Xcode workspaces for shared schemes, and using Git-Tf for checking in changes to TFS. It also covers setting up the Mac OSX build machine with Xcode command-line tools, provisioning profiles, and the Team Explorer Everywhere Command Line Client, and configuring Jenkins to poll TFS and trigger Xcode builds.
  10. Build on the Team Foundation ServiceIntroduced hosted build machines in Team Foundation Service Preview, allowing users to select a 'Hosted Build Controller' for automated compilation, testing, and packaging without manual setup. Supported all Team Build features, including gated builds and workflow customization. Output is checked into source control under $/teamproject/drops. Limited to projects with external dependencies that can be checked in or downloaded from public NuGet feeds. Supported Visual Studio 2010 SP1 and Visual Studio 11 Beta, with limitations for Windows Metro Style applications. Enabled unit testing with support for multiple frameworks, including xUnit, by checking in test adapter DLLs and configuring the build controller to find them.
  11. How to Build VB6 Apps with TFS Team Build 2010This post details how to build Visual Basic 6 applications with TFS Team Build 2010 by modifying the build workflow to replace the default 'Run MSBuild for Project' activity with one that calls VB6.exe. It references an external blog post by Richard Banks for the detailed walkthrough.