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

Build definition


VSTS provides an intuitive user interface for defining and building build definitions. A build definition comprises discrete individual steps and activities, and they together form the build process. Each project and solution has its unique requirements of the build process. Continuous integration does not provide any specification regarding what goes into a build pipeline. Continuous integration states that for it to be effective, it should have steps to ensure that the code can be compiled and its features and functionality can be tested. A build process for our Online Medicine sample application is shown here. This build pipeline comprises getting the latest version of code immediately after a developer checks-in the code, compiling code and generating binaries, executing unit tests and code coverage on the generated assembles, naming and versioning the build execution, and finally dropping the build artifacts to a location from where the release pipeline can pick and...