Continuously Integrating the Camel

Continuously Integrating the Camel

By Hugh Esco from
Date: Saturday, 12 January 2013 10:00
Duration: 50 minutes
Target audience: Any
Language: English
Tags: build ci continuous coverage deploy integration jenkins pipeline testing

Calling devops a movement in the wake of Occupy Wall Street and Tahir Square probably counts as hyperbole. Still the idea of building closer collaboration between development and operations teams nonetheless holds great promise for accelerating delivery and time to market for innovations in application development, while encouraging those practices which contribute to code stability and minimizing the sleep deprivation and anxiety associated with deployments.

This presentation will walk through the steps required to set up a Jenkins Continuous Integration server and to configure a build pipeline for use to manage the testing and deployment of a perl module.

Builds can be initiated manually or triggered by committing code to your repository. And if configured and integrated right, we can get reports from our automated test suite, on the test suite's coverage of our code base, while building a database of those results over time, and a repository of deployable artifacts from our passing tests.

Jenkins can then be used to choose among those tested options and push them to QA, UAT and production environments.


Presentation slides are published here:

Attended by: Marc Mims (‎semifor‎),