Beta Release of GitHub Support for Pipeline as Code

Written by: jglick
2 min read
Stay connected

I am happy to announce the first public beta release of a new feature suite in Jenkins and the CloudBees Jenkins Platform, part of our theme of supporting “pipelines as code.”

For background, check out my webinar of a few weeks back, Continuous Delivery as Code with Jenkins Workflow . You can see slides ( ) or watch the video ( - the demo starts at 20:30).

In a nutshell, you can now with one step create a special kind of Jenkins folder which automatically scans your GitHub organization for buildable repositories. Each repository containing a file named `Jenkinsfile` will get its own subfolder, with one Workflow project per branch. That `Jenkinsfile` is a Workflow script, and you can control your Jenkins build configuration just by editing it and pushing back to GitHub. All of the above functionality is open source and available on the experimental update center ( ) for users of Jenkins 1.609.2 and later: install Workflow: Aggregator, Workflow: Multibranch, and CloudBees GitHub Branch Source. (You will need to restart Jenkins if any dependency plugins had to be updated.)

CloudBees Jenkins Enterprise users (1.609.3.1) can enable the CJE experimental update center (Manage Jenkins » Configure System » Access to experimental plugin releases » Enable access_ and _Save) and install/update the same plugins plus CloudBees GitHub Pull Requests to get some additional GitHub features: creation of sub-projects for (forked) pull requests and notification of build status back to GitHub. If you would like to play with the features without installing anything on your production server, follow the instructions in this Docker-based demo ( ). There are many known issues and planned improvements, but enough people have been asking about this feature that we wanted to get a preview in their hands as soon as possible.

Stay up to date

We'll never share your email address and you can opt out at any time, we promise.