This article describes How to Build and deploy ASP.NET Core "MVC" Apps by using Azure DevOps Pipeline
Microsoft is a leading global vendor of computer software; hardware for computer, mobile and gaming systems; and cloud services. Microsoft's corporate headquarters is located in Redmond, Wash., and it has offices in more than 60 countries.
Microsoft Azure is an ever-expanding set of cloud services to help your organisation meet your business challenges. It’s the freedom to build, manage and deploy applications on a massive, global network using your favourite tools and frameworks.
Azure provides solutions for all industries. Bring together cloud services and products tailored for your industry to help meet your specific needs and drive innovation.
Azure Pipelines automatically builds and tests code projects to make them available to others. It works with just about any language or project type. Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build your code and ship it to any target.
Azure Pipelines is Microsoft's DevOps solution for Azure. The Build and Release services provide streamlined experiences to deploy your apps to one of Azure's many services. These services provide a continuous delivery solution if your code is managed in GitHub, Azure Repos Git or Team Foundation Version Control, or in one of the other Git servers.
Azure Pipelines supports continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build your code and ship it to any target. You accomplish this by defining a pipeline. You define pipelines using the YAML syntax or through the user interface (Classic).
Key concepts for Azure Pipelines
- A trigger tells a Pipeline to run.
- A pipeline is made up of one or more stages. A pipeline can deploy to one or more environments.
- A stage is a way of organizing jobs in a pipeline and each stage can have one or more jobs.
- Each job runs on one agent. A job can also be agentless.
- Each agent runs a job that contains one or more steps.
- A step can be a task or script and is the smallest building block of a pipeline.
- A task is a pre-packaged script that performs an action, such as invoking a REST API or publishing a build artifact.
- An artifact is a collection of files or packages published by a run.
Azure Pipelines terms
- Continuous delivery
- Continuous integration
- Deployment group
Use a pipeline to automatically build and test your .NET Core projects.
- Set up your build environment with Microsoft-hosted or self-hosted agents.
- Restore dependencies, build your project, and test with the .NET Core CLI task or a script.
- Use the publish code coverage task to publish code coverage results.
- Package and deliver your code with the .NET Core CLI task and the publish build artifacts task.
- Publish to a NuGet feed.
- Deploy your web app to Azure.
Please subscribe to support our channel.
To be aware of our new videos please subscribe our channel.