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

Understanding releases


In its simplest meaning, a release in software parlance means making software available to the end users. When a release is made, software features and functionality are made available to the end users for consumption. Releases are generally periodic in nature, and they can be done at any time-daily, weekly, monthly, yearly, or any combination of these depending on the nature of software, users, and value added into each release. A release consists of newer and updated functionality, completely tested and deployed on a production environment. Each release has a unique identifier through which it can be referred. A release is generally done on a production environment, but it can also involve deployment on multiple other environments such as test and staging. It depends on an organization as to how it would like to define a release along with the approval requirements. A release on any environment including a production environment involves getting approvals from stakeholders...