Continuous Delivery is just the beginning. The same tools can help agile software development easily in the form of Documentation Pipeline. Lightning talk in Tampere Goes Agile 2015 explains what Documentation Pipeline is and how to implement it.
8. THREE STANDARD ”TRICKS”
1. Jenkins as a swiss knife.
Jenkins has handy ”last successful artifact” URL. Bookmarkable URL to the latest documentation.
2. DB documentation in the DB metadata.
Ideal. Wide support, but rarely used? Why?
3. API docs are generated.
API docs generated. Can be something other than Swagger. 7 years ago we did it with XML schema ->
JAXB + XSLT -> HTML, which was fine then.
Editor's Notes
So what happens before the code enters the CI system?
What happens after the delivery happens?
Given that “Devops is a culture”, what support do you offer for the actual development of software?
Okay, could your developer write this on his/her own? If not, how are you going to help him/her?
Who.. DevOps people can do this. Howabout your developers? Do they have control over Jenkins? Enough experience?