{"id":1904,"date":"2018-12-04T00:00:00","date_gmt":"2018-12-04T08:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/new-azure-pipelines-announcements-vs-code-extension-github-releases-and-more"},"modified":"2023-07-28T15:46:37","modified_gmt":"2023-07-28T22:46:37","slug":"new-azure-pipelines-announcements-vs-code-extension-github-releases-and-more","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/new-azure-pipelines-announcements-vs-code-extension-github-releases-and-more\/","title":{"rendered":"New Azure Pipelines announcements \u2013 VS Code extension, GitHub Releases, and more"},"content":{"rendered":"

Since we launched Azure Pipelines in September<\/a>, we\u2019ve seen strong growth in adoption of our cloud hosted build and deployment service. We\u2019re also learning from many of the open source projects on GitHub starting to take advantage of unlimited build minutes<\/a>, and with up to 10 concurrent jobs across our hosted Linux, Widows, and Mac machines. We\u2019re seeing it make a positive difference to lots of cross-platform libraries and applications.<\/p>\n

Today at Connect();, we\u2019re announcing several new features and integrations with Azure Pipelines \u2013 two of which were directly inspired by the open source projects using Azure Pipelines to build and release their applications more easily.<\/p>\n

Azure Pipelines extension for Visual Studio Code<\/h2>\n

As we’ve built out config-as-code (aka YAML pipelines<\/a>) we\u2019ve been working in lots of our favorite open source projects to help them take advantage of the Azure Pipelines support. As we got to writing and reviewing YAML files, we quickly noticed something missing, a great editing experience in our favorite code editor \u2013 Visual Studio Code<\/a>. Like many tools, Visual Studio Code has syntax highlighting for the structure of YAML, but this requires developers to remember exactly which keys are legal where in the file. This causes developers to flip back and forth to the documentation, and the need to check for typos before committing the YAML file and trying to run the build.<\/p>\n

Enter the Azure Pipelines extension for Visual Studio Code. Now, you can have syntax highlighting and IntelliSense that’s aware of the Azure Pipelines YAML format. This means that you\u2019ll be alerted in red \u201cink\u201d if you write \u201ctasks:\u201d where you should have written \u201ctask:\u201d. IntelliSense is also schema-aware. Wherever you are in the file, press Ctrl-Space (or Cmd-Space on macOS) to see what\u2019s accepted at that point in the file.<\/p>\n

\"Azure<\/p>\n

To get started simply install the Azure Pipelines extension<\/a> from the Visual Studio Code Marketplace<\/a>. The source for the extension is open source and available on GitHub<\/a> if you\u2019d like to learn more about how it works, or want to give feedback or suggest changes.<\/p>\n

GitHub Releases<\/h2>\n

GitHub Releases are a great way to package software and ship it to end users \u2013 and they are heavily used by open source projects. We are excited to announce that you can now seamlessly manage GitHub Releases using Azure Pipelines. You can create new releases, modify drafts, or discard older ones. The new GitHub Releases task supports all the commonly performed actions like attaching binary files, publishing draft releases, and marking a releases as pre-release.<\/p>\n

\"Creating<\/p>\n

From our own experience, we know that creating release notes can sometimes be a daunting job. To help you with it, this task can automatically compute the list of changes made in this release, including links to the commits and any linked issues, and add it to release notes on GitHub.<\/p>\n

\"Release<\/p>\n

All of the built-in tasks for Azure Pipelines, including this new GitHub Releases task, are open source and available on GitHub<\/a> if you would like to suggest changes or make feature requests join us there.<\/p>\n

Azure DevOps Projects \u2013 Azure IoT support<\/h2>\n

With Azure DevOps Projects<\/a>, we try to make it easy for you to set up a fully functional DevOps pipeline straight from the Azure portal. The pipelines they create are customized to the programming language and application platform you want to use along with which Azure functionality you want to leverage and deploy to. While they are very easy and a super quick way to get started, creating a pipeline with Azure DevOps Projects in the Azure portal also tries to ensure you are set up with all the scaffolding you need to be able to grow and extend your project in the future.<\/p>\n

We have seen increasing interest from customers using Azure DevOps to build and deploy their IoT based solutions. Today we have added support in the Azure portal for Azure IoT Edge<\/a> in the Azure DevOps project workflow to make it easy to get started in those scenarios.\u00a0<\/p>\n

With support for Azure IoT Edge in Azure DevOps projects, you are able to easily get started when deploying IoT Edge modules written in Node.js, Python, Java, .NET Core, or C. Along with this, it sets up everything you would need to develop, build, and deploy your IoT Edge application including:<\/p>\n