Generate CI/CD pipeline from Visual Studio


The Azure DevOps Project simplifies the setup of an entire continuous integration (CI) and continuous delivery (CD) pipeline to Azure with Azure DevOps. You can start with existing code or use one of the provided sample applications. Then you can quickly deploy that application to various Azure services such as Virtual Machines, App Service, Azure Kubernetes Services (AKS), Azure SQL Database, and Azure Service Fabric.

Microsoft team has lunched a new visual studio extension which allows developers working in Visual Studio Code to seamlessly create, build, and deploy their apps in a continuous manner to the cloud, without leaving the editor.

It helps developers by auto-generating a CI/CD pipeline definition that takes care of building and deploying your app to the cloud with Azure. You can use Deploy to Azure extension to deploy application code present in your local system, or in Azure Repos or GitHub.

You can use this extension to set up CI/CD pipeline for every code push. It will give you an auto-generated and fully-customizable CI/CD pipeline, defined in a YAML file that is formatted for either GitHub Actions or Azure Pipelines. The YAML file is pre-populated with build and release tasks, which can be edited by the developers as needed.

In the workflow, we are also setting up Azure Pipelines and GitHub with relevant Azure-related configurations, as well as repository-related configurations, without you needing to do worry about the plumbing of the systems.


You can install extention from marketplace 
then, you can invoke it from the Command Palette (Ctrl + P or Cmd + P) > Deploy to Azure: Configure Pipeline.

Once you run the pipeline creation workflow, the extension will inspect your application’s code and generate a pipeline optimized for your project.


This was first release from Microsoft team, team will keep upgrading adding more supports to other ecosystems keep an eye on this simple and powerful VS extension, I hope you enjoyed learning. If you have any questions/feedback/issues, please write them in the comment box. 
Previous Post Next Post