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

Continuous integration process


Continuous integration is a practice based on principles. It provides guidance regarding best practices and activities that should be performed and executed. However, it does not mandate any tool, utility, product, or service. It also does not prescribe processes that should be part of the build pipeline. It just says that there should be continuous integration that starts a build pipeline automatically to verify the build aspects of the solution, the quality of the solution by executing tests, and labels the execution with a unique name for identification.

However, as a practice, there are certain aspects that are common across software development and should be used across projects. In this chapter, we used those to implement continuous integration for the sample application, OnlineMedicine. The process of continuous integration is shown in the following image:

Figure 1: Sample continuous integration process

The continuous integration process can be broken...