{"id":47122,"date":"2024-09-24T04:49:21","date_gmt":"2024-09-24T04:49:21","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=47122"},"modified":"2024-09-24T09:47:19","modified_gmt":"2024-09-24T09:47:19","slug":"azure-devops-pipelines-fundamental-tutorials","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/azure-devops-pipelines-fundamental-tutorials\/","title":{"rendered":"Azure DevOps Pipelines Fundamental Tutorials"},"content":{"rendered":"\n

Here is an in-depth, step-by-step tutorial on Azure DevOps Pipelines<\/strong> that covers everything from the fundamentals to advanced concepts. This guide is designed to help you understand the basics of pipelines, how to set them up, and how to configure them for advanced use cases such as continuous integration (CI) and continuous deployment (CD).<\/p>\n\n\n\n

1. Introduction to Azure DevOps Pipelines<\/strong><\/h3>\n\n\n\n

Azure DevOps Pipelines allow you to automate builds, tests, and deployments in a repeatable and scalable manner. It integrates well with various development languages and platforms such as .NET, Java, Node.js, Python, and more.<\/p>\n\n\n\n

Key Concepts of Pipelines<\/strong>:<\/h3>\n\n\n\n
    \n
  • Pipelines<\/strong>: Automates building, testing, and deploying your applications.<\/li>\n\n\n\n
  • Continuous Integration (CI)<\/strong>: Automates building and testing code whenever a developer commits changes.<\/li>\n\n\n\n
  • Continuous Deployment (CD)<\/strong>: Automates deploying the code to production or other environments after successful builds and tests.<\/li>\n\n\n\n
  • YAML Pipelines<\/strong>: The pipeline is defined in YAML, making it version-controllable and portable.<\/li>\n<\/ul>\n\n\n\n

    2. Setting up Azure DevOps Pipelines (Fundamentals)<\/strong><\/h3>\n\n\n\n

    Step 1: Creating a Project in Azure DevOps<\/strong><\/h4>\n\n\n\n
      \n
    1. Sign in to your Azure DevOps organization or create a new organization.<\/li>\n\n\n\n
    2. Click on New Project<\/strong>.<\/li>\n\n\n\n
    3. Name your project, select visibility (Public or Private), and click Create<\/strong>.<\/li>\n<\/ol>\n\n\n\n

      Step 2: Setting Up a Pipeline<\/strong><\/h4>\n\n\n\n
        \n
      1. Navigate to Pipelines<\/strong> \u2192 Create Pipeline<\/strong>.<\/li>\n\n\n\n
      2. Select your repository where the code is stored (e.g., GitHub, Azure Repos, Bitbucket).<\/li>\n\n\n\n
      3. Choose YAML<\/strong> or Classic Editor<\/strong> for pipeline creation:\n
          \n
        • YAML<\/strong>: Recommended for flexibility and version control.<\/li>\n\n\n\n
        • Classic Editor<\/strong>: GUI-based setup, easier for beginners.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

          Step 3: Configuring a YAML Pipeline<\/strong><\/h4>\n\n\n\n
            \n
          1. Azure DevOps will automatically detect your project type (e.g., .NET Core, Python, Node.js) and suggest a pipeline template.<\/li>\n\n\n\n
          2. Customize your YAML file. Example for a .NET Core project:<\/li>\n<\/ol>\n\n\n\n
            \n\n\n
            trigger:\n  - main\n\npool<\/span>:\n  vmImage: 'ubuntu-latest'<\/span>\n\nsteps<\/span>:\n- task: UseDotNet@2<\/span>\n  inputs<\/span>:\n    packageType: 'sdk'<\/span>\n    version<\/span>: '6.x'<\/span>\n\n- script: dotnet build\n- script: dotnet test\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            3. Pipeline Architecture & Components<\/strong><\/h3>\n\n\n\n
            Triggers<\/strong>:<\/h4>\n\n\n\n
            Triggers are used to specify when the pipeline should run. There are two primary types:<\/p>\n\n\n\n
              \n
            • CI Trigger<\/strong>: Automatically runs the pipeline when code is pushed or merged to a specific branch.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n
              trigger:\n  branches:\n    include<\/span>:\n      - main\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              Scheduled Trigger<\/strong>: Runs the pipeline at specific times.<\/p>\n\n\n\n
              \n\n\n
              schedules:\n  - cron: \"0 0 * * *\"<\/span>\n    branches:\n      include<\/span>:\n        - main\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              Pools<\/strong>:<\/h4>\n\n\n\n
              A pool defines the agent (machine) that will run your pipeline. Example:<\/p>\n\n\n
              pool:\n  vmImage: 'ubuntu-latest'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              Azure DevOps supports various agents such as Microsoft-hosted agents<\/strong> (Linux, Windows, macOS) or self-hosted agents<\/strong>.<\/p>\n\n\n\n
              Steps<\/strong>:<\/h4>\n\n\n\n
              Each pipeline is made of steps<\/strong>. These can be scripts or tasks.<\/p>\n\n\n\n
                \n
              • Script<\/strong>: Custom commands.<\/li>\n<\/ul>\n\n\n\n
                \n\n\n
                steps:\n  - script: echo<\/span> Hello, World!\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                Task<\/strong>: Predefined tasks like build, test, or deploy.<\/p>\n\n\n
                steps<\/span>:\n  -<\/span> task<\/span>: DotNetCoreCLI<\/span>@2<\/span>\n    inputs:<\/span>\n      command:<\/span> 'build'<\/span>\n      projects:<\/span> '**\/*.csproj'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                4. Advanced Features in Azure Pipelines<\/strong><\/h3>\n\n\n\n
                Multi-Stage Pipelines (CI\/CD)<\/strong>:<\/h4>\n\n\n\n
                Multi-stage pipelines split the build, test, and deployment phases across multiple stages. Each stage can be executed sequentially or in parallel.<\/p>\n\n\n\n
                Example:<\/p>\n\n\n\n
                \n\n\n
                stages:\n  - stage: Build\n    jobs:\n      - job: BuildJob\n        steps:\n          - script: echo<\/span> Building...\n\n  - stage: Deploy\n    dependsOn: Build\n    jobs:\n      - job: DeployJob\n        steps:\n          - script: echo<\/span> Deploying...\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                Environments and Approvals<\/strong>:<\/h4>\n\n\n\n
                Environments in Azure Pipelines represent the different deployment environments (e.g., Dev, QA, Prod). You can set up approvals for sensitive environments like Production.<\/p>\n\n\n\n
                Example:<\/p>\n\n\n\n
                \n\n\n
                environments:\n  - name: 'production'<\/span>\n    resourceName<\/span>: 'ProdEnvironment'<\/span>\n    approval<\/span>:\n      steps:\n        - approval: Manual\n          approvers<\/span>:\n            - user@company.com\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                Conditional Logic<\/strong>:<\/h4>\n\n\n\n
                You can set conditions in the pipeline to determine when certain steps or stages should run. Example:<\/p>\n\n\n\n
                \n\n\n
                - script: echo<\/span> This runs only on main branch\n  condition: eq(variables['Build.SourceBranch'<\/span>], 'refs\/heads\/main'<\/span>)\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                5. Pipeline Testing Strategies<\/strong><\/h3>\n\n\n\n
                Unit Tests<\/strong>:<\/h4>\n\n\n\n
                Run unit tests in your pipeline to ensure that changes do not break the application. Example for .NET Core:<\/p>\n\n\n\n
                \n\n\n
                steps<\/span>:\n  -<\/span> task<\/span>: DotNetCoreCLI<\/span>@2<\/span>\n    inputs:<\/span>\n      command:<\/span> 'test'<\/span>\n      projects:<\/span> '**\/*.Tests.csproj'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                Code Coverage<\/strong>:<\/h4>\n\n\n\n
                You can integrate code coverage tools like Cobertura or JaCoCo to report on how much of your code is covered by tests. Example (JaCoCo for Java projects):<\/p>\n\n\n\n
                \n\n\n
                steps<\/span>:\n  -<\/span> task<\/span>: Maven<\/span>@3<\/span>\n    inputs:<\/span>\n      goals:<\/span> 'verify'<\/span>\n      options:<\/span> '-Djacoco.skip=false'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                6. Continuous Deployment (CD)<\/strong><\/h3>\n\n\n\n
                Step 1: Configuring Deployments to Azure<\/strong><\/h4>\n\n\n\n
                Azure DevOps integrates easily with various deployment platforms such as Azure App Services<\/strong>, AKS (Kubernetes)<\/strong>, Virtual Machines<\/strong>, or Containers<\/strong>.<\/p>\n\n\n\n
                Example for deploying to Azure App Service:<\/p>\n\n\n\n
                \n\n\n
                steps<\/span>:\n  -<\/span> task<\/span>: AzureRmWebAppDeployment<\/span>@4<\/span>\n    inputs:<\/span>\n      azureSubscription:<\/span> '<your-service-connection>'<\/span>\n      appName:<\/span> '<your-app-service-name>'<\/span>\n      package:<\/span> '$(System.DefaultWorkingDirectory)\/drop\/*.zip'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                \n\n\n\n
                Step 2: Rolling Back Deployments<\/strong><\/h4>\n\n\n\n
                If the deployment fails, you can automatically roll back to the previous version by setting rollback conditions.<\/p>\n\n\n\n
                7. Pipeline Variables & Secrets Management<\/strong><\/h3>\n\n\n\n
                Variables<\/strong>:<\/h4>\n\n\n\n
                Variables in Azure Pipelines allow you to store values that can be reused across multiple steps.<\/p>\n\n\n\n
                \n\n\n
                variables:\n  buildConfiguration: 'Release'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                Secret Variables<\/strong>:<\/h4>
                Sensitive values like API keys can be stored as secret variables.<\/p><\/p>\n\n\n
                variables:\n  - name: 'API_KEY'<\/span>\n    value: '$(API_KEY)'<\/span>  # Referenced securely<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                8. Best Practices for Azure DevOps Pipelines<\/strong><\/h3>\n\n\n\n
                  \n
                • Use YAML Pipelines<\/strong>: YAML pipelines are easier to version and maintain than classic pipelines.<\/li>\n\n\n\n
                • Break Down Pipelines<\/strong>: Split pipelines into smaller stages for faster feedback.<\/li>\n\n\n\n
                • Parallel Jobs<\/strong>: Use parallel jobs for steps that are independent, reducing pipeline execution time.<\/li>\n\n\n\n
                • Environment-Specific Variables<\/strong>: Use variable groups or pipeline environments for managing configuration values for different environments.<\/li>\n\n\n\n
                • Automate Rollbacks<\/strong>: Implement automatic rollback strategies in case a deployment fails.<\/li>\n<\/ul>\n\n\n\n
                  1. Advanced Pipeline Triggers<\/strong><\/h3>\n\n\n\n
                  While basic triggers (CI and scheduled triggers) are common, advanced use cases require more sophisticated triggering mechanisms.<\/p>\n\n\n\n
                  Path-Based Triggers<\/strong>:<\/h4>\n\n\n\n
                  You can configure pipelines to trigger only when changes occur in specific files or directories.<\/p>\n\n\n\n
                  \n\n\n
                  trigger:\n  branches:\n    include<\/span>:\n      - main\n  paths:\n    include<\/span>:\n      - src\/**\n    exclude:\n      - docs\/**\n<\/span><\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  \n\n\n\n
                  Tag-Based Triggers<\/strong>:<\/h4>\n\n\n\n
                  To trigger pipelines based on Git tags, useful for triggering deployment pipelines after tagging a release.<\/p>\n\n\n
                  trigger:\n  tags:\n    include<\/span>:\n      - v*\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Pipeline Triggering Other Pipelines<\/strong>:<\/h4>\n\n\n\n
                  You can chain multiple pipelines together by triggering one pipeline after another.<\/p>\n\n\n
                  resources:\n  pipelines:\n    - pipeline: buildPipeline\n      source<\/span>: 'BuildPipeline'<\/span>\n      trigger<\/span>: true<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  2. Multi-Stage Pipelines for End-to-End CI\/CD<\/strong><\/h3>\n\n\n\n
                  Multi-stage pipelines are a crucial feature that allows splitting the pipeline into various build<\/strong>, test<\/strong>, and deployment stages<\/strong>. This ensures clear separation of concerns and flexibility in the deployment process.<\/p>\n\n\n\n
                  Example: Multi-Stage CI\/CD Pipeline for a Web Application<\/strong><\/h4>\n\n\n
                  trigger:\n  branches:\n    include<\/span>:\n      - main\n\nstages:\n  - stage: Build\n    jobs:\n      - job: BuildJob\n        pool:\n          vmImage: 'ubuntu-latest'<\/span>\n        steps:\n          - task: DotNetCoreCLI@2<\/span>\n            inputs:\n              command: 'build'<\/span>\n              projects: '**\/*.csproj'<\/span>\n          - task: PublishBuildArtifacts@1<\/span>\n            inputs:\n              pathToPublish: $(Build.ArtifactStagingDirectory)\n              artifactName: drop\n\n  - stage: Test\n    dependsOn: Build\n    jobs:\n      - job: TestJob\n        pool:\n          vmImage: 'ubuntu-latest'<\/span>\n        steps:\n          - task: DotNetCoreCLI@2<\/span>\n            inputs:\n              command: 'test'<\/span>\n              projects: '**\/*.Tests.csproj'<\/span>\n\n  - stage: Deploy\n    dependsOn: Test\n    condition: succeeded()\n    jobs:\n      - job: DeployJob\n        pool:\n          vmImage: 'ubuntu-latest'<\/span>\n        steps:\n          - script: echo<\/span> Deploying to production\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  This example demonstrates how to break the pipeline into build<\/strong>, test<\/strong>, and deployment stages<\/strong>, with dependencies and conditions to ensure smooth flow.<\/p>\n\n\n\n
                  Advanced Stage Dependencies<\/strong>:<\/h4>\n\n\n\n
                  You can create complex dependencies between stages using conditions. For example, skip a stage if the previous one fails.<\/p>\n\n\n
                  condition<\/span>: always()\n<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
                  3. Deployment Strategies<\/strong><\/h3>\n\n\n\n
                  Azure Pipelines support a variety of deployment strategies to ensure safe and efficient releases.<\/p>\n\n\n\n
                  Rolling Deployments<\/strong>:<\/h4>\n\n\n\n
                  Rolling deployments gradually replace instances of your service with the new version, reducing downtime.<\/p>\n\n\n
                  steps<\/span>:\n  -<\/span> task<\/span>: AzureRmWebAppDeployment<\/span>@4<\/span>\n    inputs:<\/span>\n      azureSubscription:<\/span> '<subscription>'<\/span>\n      WebAppName:<\/span> '<app-service>'<\/span>\n      DeploymentMethod:<\/span> 'rolling'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Canary Deployment<\/strong>:<\/h4>\n\n\n\n
                  Canary deployments send a small percentage of traffic to the new version to ensure the changes work as expected before rolling them out entirely.<\/p>\n\n\n\n
                  This often involves external services like Azure Traffic Manager<\/strong> or custom traffic-routing logic. Integration can be done with custom pipeline logic or by using additional Azure App Services<\/strong> for traffic splitting.<\/p>\n\n\n\n
                  4. Pipeline Templates for Reusability<\/strong><\/h3>\n\n\n\n
                  For teams working on multiple pipelines, it is useful to create templates that can be reused across pipelines. Templates allow you to define jobs, steps, or entire pipelines that can be imported into other pipelines.<\/p>\n\n\n\n
                  Pipeline Template Example<\/strong>:<\/h4>\n\n\n\n
                  Define a reusable build step:<\/p>\n\n\n
                  # templates\/build-template.yml<\/span>\nparameters:\n  - name: buildConfiguration\n    type: string\n    default<\/span>: 'Release'<\/span>\n\nsteps:\n  - script: |\n      echo<\/span> Build project in ${{ parameters.buildConfiguration }} mode.\n      dotnet build --configuration ${{ parameters.buildConfiguration }}\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Using the Template<\/strong>:<\/p>\n\n\n
                  # azure-pipelines.yml<\/span>\nstages:\n  - stage: Build\n    jobs:\n      - template: templates\/build-template.yml\n        parameters:\n          buildConfiguration: 'Debug'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  5. Advanced Environment Management & Approvals<\/strong><\/h3>\n\n\n\n
                  Azure DevOps pipelines support environments<\/strong> that represent different stages in the deployment lifecycle (e.g., Dev, QA, Staging, Production).<\/p>\n\n\n\n
                  Defining Environments<\/strong>:<\/h4>\n\n\n
                  environments:\n  - name: 'production'<\/span>\n    resourceName<\/span>: 'ProdAppService'<\/span>\n    protectionRules<\/span>:\n      - approvals:\n          steps:\n            - approvers: [user1@company.com, user2@company.com]\n              timeoutInMinutes<\/span>: 30<\/span>\n              approvalType<\/span>: 'Manual'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  This ensures that any deployment to production requires a manual approval from specified stakeholders.<\/p>\n\n\n\n
                  Advanced Approvals and Gates<\/strong>:<\/h4>\n\n\n\n
                  Gates provide checks that must be passed before deployment can proceed. This can include external APIs, system health checks, or compliance scans.<\/p>\n\n\n\n
                  Example of using a REST API gate:<\/p>\n\n\n
                  gates:\n  - gate: RestApiGate\n    inputs<\/span>:\n      method: GET\n      url<\/span>: 'https:\/\/healthcheck.yourdomain.com\/api\/status'<\/span>\n      successCriteria<\/span>: eq(root['status'<\/span>], 'healthy'<\/span>)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  6. Secret and Secure File Management<\/strong><\/h3>\n\n\n\n
                  Handling sensitive data is critical in CI\/CD pipelines. Azure DevOps offers Azure Key Vault<\/strong> integration to securely manage secrets and credentials.<\/p>\n\n\n\n
                  Accessing Secrets from Azure Key Vault<\/strong>:<\/h4>\n\n\n
                  variables:\n  - group: MyVariableGroup\n  - name: 'API_KEY'<\/span>\n    value<\/span>: $(API_KEY)\n  - name: 'KEY_VAULT_SECRET'<\/span>\n    value<\/span>: $(MySecret)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  7. Parallel Jobs & Matrix Builds<\/strong><\/h3>\n\n\n\n
                  In many cases, especially when working on large projects, running builds in parallel can significantly reduce build time.<\/p>\n\n\n\n
                  Matrix Builds<\/strong>:<\/h4>\n\n\n\n
                  Matrix builds allow you to run the same job with different configurations in parallel.<\/p>\n\n\n
                  strategy:\n  matrix:\n    Linux:\n      vmImage: 'ubuntu-latest'<\/span>\n      configuration<\/span>: 'Debug'<\/span>\n    Windows<\/span>:\n      vmImage: 'windows-latest'<\/span>\n      configuration<\/span>: 'Release'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  8. Pipeline Caching and Artifacts<\/strong><\/h3>\n\n\n\n
                  Azure Pipelines support caching to reduce pipeline run times by storing dependencies between builds.<\/p>\n\n\n\n
                  Caching Dependencies<\/strong>:<\/h4>\n\n\n\n
                  steps:  - task: Cache@2    inputs:      key: 'npm | \"$(Agent.OS)\" | package-lock.json'      path: 'node_modules'      restoreKeys: |        npm | \"$(Agent.OS)\"<\/pre>\n\n\n\n
                  Using Build Artifacts<\/strong>:<\/h4>\n\n\n\n
                  Artifacts are files or packages generated by your build that can be shared or deployed.<\/p>\n\n\n\n
                  steps:  - task: PublishBuildArtifacts@1    inputs:      pathToPublish: $(Build.ArtifactStagingDirectory)      artifactName: 'drop'<\/pre>\n\n\n\n
                  9. Integrating with External Tools<\/strong><\/h3>\n\n\n\n
                  Azure Pipelines can be integrated with third-party services like Slack<\/strong>, Jira<\/strong>, or ServiceNow<\/strong>.<\/p>\n\n\n\n
                  Slack Notifications<\/strong>:<\/h4>\n\n\n\n
                  Azure Pipelines can send build notifications directly to your Slack channels.<\/p>\n\n\n
                  steps<\/span>:\n  -<\/span> task<\/span>: SlackNotification<\/span>@1<\/span>\n    inputs:<\/span>\n      slackConnection:<\/span> 'MySlackServiceConnection'<\/span>\n      message:<\/span> 'Build completed'<\/span>\n      channel:<\/span> '#devops'<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  0. Optimizing Pipeline Performance<\/strong><\/h3>\n\n\n\n
                  Best Practices<\/strong>:<\/h4>\n\n\n\n
                    \n
                  • Use Hosted Agents for Speed<\/strong>: Leverage Microsoft-hosted agents for faster setup and execution, or use self-hosted agents for specialized environments.<\/li>\n\n\n\n
                  • Limit Resource Usage<\/strong>: Avoid unnecessary resource allocation by using pipeline stages and jobs efficiently.<\/li>\n\n\n\n
                  • Parallel Execution<\/strong>: Run independent jobs in parallel to speed up builds.<\/li>\n\n\n\n
                  • Cache External Dependencies<\/strong>: Use caching for dependencies like npm, NuGet, or Docker images.<\/li>\n<\/ul>\n\n\n\n
                    Resource Limiting<\/strong>:<\/h4>\n\n\n\n
                    To prevent resource waste:<\/p>\n\n\n
                    jobs:\n  - job: Build\n    pool<\/span>:\n      vmImage: 'ubuntu-latest'<\/span>\n    timeoutInMinutes<\/span>: 20<\/span>\n    cancelTimeoutInMinutes<\/span>: 5<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>","protected":false},"excerpt":{"rendered":"
                    Here is an in-depth, step-by-step tutorial on Azure DevOps Pipelines that covers everything from the fundamentals to advanced concepts. This guide is designed to help you understand… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-47122","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=47122"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47122\/revisions"}],"predecessor-version":[{"id":47125,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/47122\/revisions\/47125"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=47122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=47122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=47122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}