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

Configuring assembly version info in build pipelines  


Azure DevOps Server provides a high level of traceability that makes it really easy to track builds generated from a build definition through to pull request, to code changes, and finally, back to work items. This traceability is, however, lost at the point when the binaries are generated through the build. Wouldn't it be great if you could look at the binaries deployed in an environment and identify the build they originated from? This could prove to be really useful when testing for regression issues. You can also take it a step further and display the binary version in the application, so when users log issues against your application they can also report the version of the application they are seeing the issues in. In this recipe, we'll learn how to configure the build number in the assemblies generated through a build pipeline.    

Getting ready

The marketplace features the Assembly Info extension. This open source task, created by...