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

Principles of Continuous Integration


Continuous integration is a mindset and guidance. It is based on certain principles, which make it highly effective. It does not prescribe ways to implement itself. Continuous integration does not talk of any individual tool, technology, or utility. It also does not mention the tasks that should be part of any continuous integration. However, it mentions that basic activities should be performed for effective continuous integration.

Automation

It is difficult to achieve continuous integration goals when implemented and executed manually. Automation should be used for implementing continuous integration. There should be a source code repository for developers to collaborate on code, an automated build pipeline that has the capability of executing both on demand as well as on triggers. It should also have the capability to execute build pipelines on schedule. Furthermore, the activities in build pipelines should have capabilities to compile the code, perform...