Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Continuous Documentation With Jenkins, Asciidoctor, and Gradle [Video]

DZone's Guide to

Continuous Documentation With Jenkins, Asciidoctor, and Gradle [Video]

Putting together a pipeline for integrating documentation delivery into your regular build process.

· DevOps Zone
Free Resource

In response to accelerated release cycles, a new set of testing capabilities is now required to deliver quality at speed. This is why there is a shake-up in the testing tools landscape—and a new leader has emerged in the just released Gartner Magic Quadrant for Software Test Automation.

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.


Recently published 5th annual Software Fail Watch Report identified 606 recorded software fails impacting half of the world’s population (3.7 billion people), $1.7 trillion in assets, and 314 companies. Our advice: Rethink your testing strategies and approach to quality so they’re not finding it in your next release.

Topics:
continuous software delivery ,documentation

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.urlSource.name }}