Last year I shared my thoughts on Jenkins pipelines and provided a walkthrough of how we’re using pipelines at Mozilla. Since then, the Pipeline Model Definition plugin has came out of beta, and we’ve been migrating our pipelines to the new declarative syntax with a shared library.
Read More »Migrating to declarative Jenkins pipelinesI’ve recently been migrating Mozilla’s traditional Jenkins jobs for functional UI testing of our web properties into pipelines. The following describes some of the common features of these pipelines. I’ve included my reasons for these design choices, and highlighted limitations that I’m hoping will be resolved as pipelines evolve. I’ve also written a post on my thoughts on Jenkins pipelines and IRC notifications in Jenkins pipelines.
Read More »Jenkins pipeline walkthroughBefore Jenkins pipelines, all job configuration was stored as XML on the server, and only configurable via the web dashboard. There are a number of limitations to this approach. A few that come to mind are:
Read More »My thoughts on Jenkins pipelinesI’ve been migrating several of our Jenkins jobs to pipelines, and one of the challenges was preserving our IRC notifications whenever a build result changes. At this time, the IRC plugin for Jenkins doesn’t include support for pipelines, however it is still possible to trigger a notification using the sh step. The following snippet connects to irc.mozilla.org and sends a build result notice to #fx-test-alerts: