If you hear someone talking about Gerrit, 99 times out of a 100 they will turn the discussion to their Jenkins setup (and oh boy, do I love speaking about Jenkins setups for different workflows!).
We are happy to release Jenkins Assembla Merge Request builder (or JAMRb
for short) as an open source project to the Assembla and Jenkins communities.
JAMRb allows you to easily manage Jenkins’ jobs for all your merge requests:
- Set up template jobs (build, deploy, test) for your mainline and these jobs will be automatically created for any merge request in the project.
- Merge request got merged or ignored? JAMRb will clean up its jobs without the necessity to bother your Jenkins’ administrators.
- Want to build the future of your merge request before you merge, not just branches that they are based on? JAMRb will configure Build Parameters for target branch and use the remote of a merge request, so just before build you can verify if merge request applies without errors, otherwise fail build.
- Works fine with Assembla's Jenkins Auth plugin.
Just to give you a little taste of this, if your merge request view looks like this:
Jenkins before JAMRb:
Jenkins with JAMRb (extra jobs created automatically):
At the moment, this workflow only applies to git, however, merge requests for Subversion are already in beta. If you are using Assembla and SVN (or Perforce) and are interested in this setup, let us know in the comments.
A while ago we changed our CI server to Jenkins
at Assembla. We loved Jenkins at first sight and never looked back, and we are happy to officially announce an Auth Plugin for Jenkins.
There is a burden that usually comes when adopting a new service - maintaining a set of users and permissions in every external service can get out of hand very quickly. Thats why we are introducing Assembla Auth plugin for Jenkins
- set it up once (no longer than 10 minutes) and your authentication and authorization will be delegated to Assembla (thats all done via our new API
, check it out too). You will no longer need to worry about:
- Adding a new team member - a Jenkins user automatically gets created when user tries to access Jenkins for the first time with permissions delegated to Assembla
- Promotions - member upgraded to an owner of your Assembla space? No worries, this permission will propagate to Jenkins in less than a minute
- Saying goodbye - someone is leaving your team? We've got that covered, user will lose access to your Jenkins as soon as he loses access to your Assembla space.
Look for "Assembla Auth" plugin v1.02 in your Jenkins plugin manager and try it out. We've been using it for a couple of weeks now and it works like a charm.
We are releasing this plugin as open source - https://www.assembla.com/code/assembla-oss/git/nodes
- feel free to watch that space - we'll be adding more of Assembla's open source stuff there. If you are interested in contributing - we are eagerly awaiting first merge requests
. If you notice any issues, please file a ticket
P.S. If you manage to lock yourself out of your Jenkins, here is a handy guide to disable security
for a moment.