Book Image

Azure DevOps Server 2019 Cookbook - Second Edition

By : Tarun Arora, Utkarsh Shigihalli
Book Image

Azure DevOps Server 2019 Cookbook - Second Edition

By: Tarun Arora, Utkarsh Shigihalli

Overview of this book

Previously known as Team Foundation Server (TFS), Azure DevOps Server is a comprehensive on-premise DevOps toolset with a rich ecosystem of open source plugins. This book will help you learn how to effectively use the different Azure DevOps services. You will start by building high-quality scalable software targeting .NET, .NET Core and Node.js applications. Next, you will learn techniques that will help you to set up end-to-end traceability of your code changes, from design through to release. Whether you are deploying software on-premise or in the cloud in App Service, Functions, or Azure VMs, this book will help you learn release management techniques to reduce failures. As you progress, you will be able to secure application configuration by using Azure Key Vault. You will also understand how to create and release extensions to the Azure DevOps marketplace and reach the million-strong developer ecosystem for feedback. Later, the working extension samples will even allow you to iterate changes in your extensions easily and release updates to the marketplace quickly. By the end of this book, you will be equipped with the skills you need to break down the invisible silos between your software development teams, and transform them into a modern cross-functional software development team.
Table of Contents (14 chapters)
Title Page
About Packt
Contributors
Preface
Index

Publishing extensions to the marketplace


For extensions to be used in the Azure DevOps Server/Service, extensions need to be published to the VS Marketplace. As highlighted at the beginning of this chapter, VS Marketplace is the one-stop shop for extensions - tools that extend Azure DevOps. 

In all the recipes we worked through in this chapter, we created various types of extensions. However, one thing we have not done is to publish the extensions we created to the marketplace. 

Extensions can be published in either public or private visibility modes. Extension visibility is controlled via a public flag in the manifest file. To make an extension usable and visible to the public, you need to mark the extension as public by setting the flag in the manifest as shown:

{
 "public": true
 }

Note

The default visibility, if you do not specify in the manifest file, is private. This means the published private extension is visible to the publisher and the publisher of the collection has access too. Similarly...