Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
DevOps with Windows Server 2016

You're reading from   DevOps with Windows Server 2016 Obtain enterprise agility and continuous delivery by implementing DevOps with Windows Server 2016

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher Packt
ISBN-13 9781786468550
Length 558 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
 Modi Modi
Author Profile Icon Modi
Modi
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface
1. Introducing DevOps FREE CHAPTER 2. DevOps Tools and Technologies 3. DevOps Automation Primer 4. Nano, Containers, and Docker Primer 5. Building a Sample Application 6. Source Code Control 7. Configuration Management 8. Configuration Management and Operational Validation 9. Continuous Integration 10. Continuous Delivery and Deployment 11. Monitoring and Measuring

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images