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

Testing a NuGet package using Artifact views


As mentioned in the previous recipe, packages are immutable. This means that package versions are reserved as soon as you publish them to the feed. You cannot publish the same version of the package again.

Semantic versioning ensures that versions correctly convey the change. The version numbers are in Major.Minor.Patch format and, optionally, can contain additional labels such as 1.0.0-alpha or 1.0.0-beta:

  • The MAJOR version is used when you make incompatible API changes
  • The MINOR version when you add functionality in a backward-compatible manner
  • The PATCH version is used when you make backward-compatible bug fixes

Additional labels for prerelease and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

However, with the NuGet package, proper testing can be done only after it has been packaged and versioned.

In this recipe, we will see how we can use artifact views to consume prerelease packages and eventually promote them after...