Abstract
The previous chapters have demonstrated the automation of the essential steps from source code to deployment: build, distribution, and deployment. What’s missing now is the glue that holds them all together: polling the source code repositories, getting packages from the build server to the repository server and generally controlling the flow, aborting the pipeline instance when one step has failed, and so on.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
- 2.
The <ant> and <rake> tasks execute the specialized builders of the same name and allow you to specify targets and build files. See https://docs.gocd.org/current/configuration/configuration_reference.html#ant for more information.
- 3.
- 4.
- 5.
- 6.
- 7.
Starting from GoCD version 16.7, pipeline configurations can be swapped out to external version control repositories and, through plug-ins, can even be written in different formats, such as YAML. While this seems like a very promising approach, introducing it is outside the scope of this book.
- 8.
- 9.
- 10.
- 11.
Wikipedia, “Cargo cult programming,” https://en.wikipedia.org/wiki/Cargo_cult_programming , 2018.
- 12.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2019 Moritz Lenz
About this chapter
Cite this chapter
Lenz, M. (2019). Building in the Pipeline with Go Continuous Delivery. In: Python Continuous Integration and Delivery. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4281-0_9
Download citation
DOI: https://doi.org/10.1007/978-1-4842-4281-0_9
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-4280-3
Online ISBN: 978-1-4842-4281-0
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)