My exposure to Jenkins and its usage over the years has been patchy at best. During this time, however, I’ve had some degree of experience as a user of various continuous delivery (CD) tools like Jenkins and am reasonably familiar with the advantages these tools can offer software development teams.

I’ve also found that while many software developers are familiar with the broader concept of "developer operations" (or simply "devops"), fewer seem familiar with the concepts of CD and related tools to facilitate devops within organizations.

The CD process is based on the fundamental flow of building the application > testing it > delivering it, where typically:

Now, as one of the major contributors to the Jenkins User Documentation (and faced with a reasonably steep learning curve), it quickly became apparent about the lack of accessible documentation to hand-hold people relatively new to Jenkins through this CD process. I couldn’t find anything in the Jenkins User Documentation to demonstrate how Jenkins implements this process on a simple app that delivers an end result.

With the guidance and assistance of helpful colleagues, I therefore decided to embark on creating a series of Jenkins tutorials to help fill these documentation and knowledge gaps. These tutorials are based on Daniele Procida’s description of how tutorials should be presented in his blog post "What nobody tells you about documentation").

You can access all currently available tutorials from the Tutorials overview page in the Jenkins User Documentation. It’s worthwhile checking that page from time to time as it’ll be updated whenever a new tutorial is published.

Also, if you have any suggestions for tutorials or other content you’d like to see in the documentation, please post your suggestions in the Jenkins Documentation Google Group, which you can also post (and reply) to by emailing jenkinsci-docs@googlegroups.com.