Continuous Documentation With Jenkins, Asciidoctor, and Gradle [Video]
Continuous Documentation With Jenkins, Asciidoctor, and Gradle [Video]
Putting together a pipeline for integrating documentation delivery into your regular build process.
Join the DZone community and get the full member experience.
Join For FreeDownload the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.
Probably all of you are using CI/CD for building and delivering your applications. Some of the steps that a continuous delivery pipeline is typically composed are compile step, tests step, acceptance tests step, static code analysis, …
But one step that is usually missed is the documentation step. In this screencast you will learn how to integrate the documentation process to your continuous delivery pipeline using Jenkins, Asciidoctor and Gradle.
Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.
Like This Article? Read More From DZone
Published at DZone with permission of Alex Soto Bueno , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}