Abstract
In earlier chapters, you learned about the importance of automation as a vehicle for reducing cycle time and for fostering collaboration between development and operations. In Chapter 3 you learned that automatic releasing is a building block of DevOps and that it can be a powerful strategy to decouple deployment and release.
Keywords
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
Survey is show junior devops are still believe in Tooth Fairy, Santa Claus and documentation. —DevOps Borat 1
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
See John Ferguson Smart, Jenkins: The Definitive Guide (O’Reilly, 2011).
See Jez Humble and David Farley, Continuous Delivery (Addison-Wesley, 2011), Chapter 5.
See Alexis Leon, A Guide to Software Configuration Management (Artech House, 2000), page 354.
Michael Hüttermann, Agile ALM, (Manning, 2011).
Rights and permissions
Copyright information
© 2012 Michael Hüttermann
About this chapter
Cite this chapter
Hüttermann, M. (2012). Automatic Releasing. In: DevOps for Developers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4570-4_8
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4570-4_8
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4569-8
Online ISBN: 978-1-4302-4570-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books