App Build / CI Pipeline

This introductory tutorial will walk through setting up ADO Pipelines using pipeline-as-code with yaml.

Estimated time to complete: 3 hours

---

Overview

You will onboard a DotNet Core app onto ADO's Pipeline using the pipeline editor in yml, including building, testing, packaging, and archiving. In the continuous delivery GitOps model, this pipeline is the application build / CI (continuous integration) pipeline, where deployments occur in a separate deploy pipeline.

Requirements

• We will use the pipeline editor in ADO (no local setup needed)
• Referenced content:
  • Pipelines
  • Artifacts
  • Ticket-based Engineering

Setup

Create a fork from the App CI Pipeline lab to work on your own Git repo.

Create a new ticket as a Product Backlog Item in ADO Boards within the Dojo Sandbox under the Pipelines App CI lab feature. You can copy/paste the ticket details from the feature.

By using the Pipeline editor for this lab, we will create a branch as we write the pipeline. We will then link our work item to this branch during the pull request.

When creating pipelines, teams often will commit directly to main in order to get faster feedback on a main branch build. For this lab, we will create a branch and submit a pull request.