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

The principles of continuous deployment


Like continuous integration, continuous delivery and deployment is a culture, mindset, and guidance. It is based on adopting principles, which makes releasing applications and their life cycle efficient and effective. Some of the important principles are discussed next.

Automation as an enabler

It is difficult to achieve the benefits of continuous deployment and delivery when executed manually. It is important that automation is used to achieve their intent. Efforts should be made to automate every step and at the minimum should retrieve the artifacts generated by the build pipeline, execute deployment activities on multiple environments, and allow for the approval workflow before moving and deploying from one environment to another. There should be an automated release pipeline that has the capability of execution both on demand as well as based on triggers. It should also have the capability to execute release pipelines on the schedule. Furthermore...