Book Image

DevOps with Windows Server 2016

Book Image

DevOps with Windows Server 2016

Overview of this book

Delivering applications swiftly is one of the major challenges faced in fast-paced business environments. Windows Server 2016 DevOps is the solution to these challenges as it helps organizations to respond faster in order to handle the competitive pressures by replacing error-prone manual tasks using automation. This book is a practical description and implementation of DevOps principles and practices using the features provided by Windows Server 2016 and VSTS vNext. It jumps straight into explaining the relevant tools and technologies needed to implement DevOps principles and practices. It implements all major DevOps practices and principles and takes readers through it from envisioning a project up to operations and further. It uses the latest and upcoming concepts and technologies from Microsoft and open source such as Docker, Windows Container, Nano Server, DSC, Pester, and VSTS vNext. By the end of this book, you will be well aware of the DevOps principles and practices and will have implemented all these principles practically for a sample application using the latest technologies on the Microsoft platform. You will be ready to start implementing DevOps within your project/engagement.
Table of Contents (20 chapters)
DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface

Types of releases


There are two ways in which VSTS can be configured to execute releases:

  • Scheduled release
  • Continuous deployment

We have been discussing continuous deployment in this chapter, and the next section talks about scheduled releases.

Scheduled releases

A scheduled release refers to automatic release pipeline execution at a predetermined schedule. Multiple schedules can be configured for each release pipeline and can include multiple source repositories. The release pipeline will execute at a given schedule and is not dependent on changes done to the code in the repository. These types of release pipelines are generally used on weekends during off-hours when generally there is no activity on the repository. The scheduling of a release is shown in Figure 3.

Figure 3: Scheduled release pipeline

In Figure 3, a release has been scheduled to run at 3 a.m. on Monday, Tuesday, Wednesday, Thursday, and Friday.

Continuous deployment

Continuous deployment refers to the execution of release pipeline...