Multi-Stage CI/CD Pipelines as Code with YAML For Azure DevOps


    This video will focus on how to use CI/CD Pipelines as Code with YAML for Azure Pipelines. How to create a Multi-stage pipeline using YAML file. It will provide Pipelines as Code with YAML tutorial for Beginners | Multi-stage Azure Pipelines training.

    Learn a complete tutorial for creating the Continuous Integration and Continuous Deployment pipelines as Code using YAML configuration Language.

    This will cover, creating the application infrastructure on the cloud with Azure SQL, Azure Service Plan, Azure SQL Server and configure firewall rule to allow Azure Web App to communicate with Azure SQL Server.

    Also, how to create a new YAML pipeline from Azure DevOps pipelines template for ASP.NET which include tasks in YAML that restore all the NuGet packages, build the ASP.NET application and running unit test, create Web.Zip of the app and store that on Azure Artifacts then pick this package and deploy it to the Web App and SQL Server on Azure.

    Using YAML (Yet Another Markup Language). This allows us to access pipeline features as but with a markup file that can be managed like any other source control file. YAML build definitions can be added to a project by simply adding their source file to the root of the repository. Azure DevOps also provides default templates for popular project types, as well as a YAML designer to simplify the process of defining build and release tasks.

    About the Author




    # Multi-stage #Azure #Azure_Pipelines_tutorial #Azure_training #Azure_DevOps #YAML

    Links in the video


    Previous articleCreating a Static Website in S3 with AWS CloudFormation
    Next articleJenkins Interview Questions | Top 50 Jenkins Interview Questions and Answers | Edureka


    1. Thanks for sharing your knowledge, i am facing one issue while downloading the the artifact from source file, below is the job. it says
      [error]Build type 'D:toolsagent_work181sdist' is not recognized.

      – task: [email protected]

      displayName: Download Build Artifact (EAR)


      source: $(Pipeline.Workspace)sdist

      artifact: "reps"

      pipeline: 20

      path: $(Build.ArtifactStagingDirectory)

    2. Thanks a lot for detailed explanation but when following this method css,img,fonts and other few files are missing during build, when i change drop location to $(build.SourcesDirectory) no files are missing but getting error ##[error]Error: No package found with specified pattern: D:a1adrop*.zip<br/>Check if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.

    3. Hi, I am going thru a multi stage deployment(Dev-PPE-Prod) in CD pipeline where i have 1 web.config & 1 xyz.js file needs to be excluded from the deployment process. i know there is something called "Additional Arguments" under IIS Web App Deploy task in CD phase but not sure how to do this. Would appreciate your help on this

    4. I'm usually using the classic view for developing the pipelines. But now I'd say it looks more clean when working with yaml files directly than classic (but this is more of a preference I guess). Using a yaml means you can track changes easier if you keep them in a repository.