We’ve been running Jenkins for our automatic testing for more than a year now, using Jenkins Job Builder as a way to automate the creation and updating of the many jobs. While the scale was still reasonably small (order of 100 jobs), I often encountered problems managing the job definitions this way.
I had long been hoping for some Travis-like way to configure jobs from inside the code repository, and give the power (and responsibility) back to the developer.
Jenkins 2 and pipelines
Earlier this year, Jenkins 2 was released, which included exactly this thing: Jenkinsfiles. This is a single file you put at the root of your code repository, which is then parsed by Jenkins. This feature was a continuation of the “workflow” suit of plugins, renamed to “pipelines” and included in the core install of Jenkins.
The Jenkinsfile is written in a DSL on top of Groovy, and has the potential to contain the complete job definition as you would have done before through the Web UI. Support for pipelines has to be implemented in every other plugin (if relevant), so adoption took some time.
Because of the way I deploy the Jenkins master, it was upgraded by accident. However, it did not work (did not even start):
SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.Ajp13ConnectorFactory
Reading the upgrade notes confirmed ajp support was removed:
Jenkins 2 no longer supports AJP with the embedded Winstone-Jetty container, so if you’re using Jenkins with a reverse proxy, please make sure it uses HTTP before upgrading.
My limited knowledge of
ajp, lack of time to investigate, and - honestly - not realising the use of the pipelines at the time, made me do the wrong thing: downgrade the master to “latest-lts” and keep it there for the time being.
Many months later, I finally picked up the task to upgrade the master to 2.0. That’s when I realised we had simply never used the ajp connector for Jenkins… I removed the parameter and behold: it just worked. Nothing that we used in v1 appeared broken, nobody noticed anything (well, at least nobody complained, which is usually my metric).
Our migration to pipelines
Since plugins have to support pipelines to be usable this way, this can be a delaying factor for adoption. You can look for alternative plugins that implement the functionality (and do support pipelines), reimplement the functionality yourself by writing some Groovy classes, or maybe help the maintainer and donate some time to create a PR. Our realize you didn’t need the plugin in the first place.
All plugins essential to our setup support pipelines, so we can actually migrate all our jobs to pipeline jobs. Since I was using the Jenkins Job Builder before, most jobs are based on one of a small set of templates, and therefore I only had to convert those templates to Groovy classes and include them with every job.
The converted templates where never identical (parameters), so extensive testing of the new jobs by the code owner was obviously necessary. Against my expectations, most developers were actually very responsive to this major change in their workflow and were very cooperative. Some actually helped write part of the Groovy classes and fixed some bugs for me (I suspect they were really just happy to take a break from their usual projects).
After the first week, half of the jobs (mostly my own) were converted. After the second week, about 75% of the jobs was using pipelines. The remaining jobs are still in the process of slowly being tested and converted at a slow pace.
I’m working on some posts detailing the implementation of pipelines for our organisation.
comments powered by Disqus