@dsaff 
Regarding the tags and release management in CloudBees. The tags do not need to be specified by you in GitHub manually. You can specify it together with new versions and starting the build + deployment in one step in Jenkins.

Maybe you didn't see the discussion (setting release and dev version variables) from yesterday morning.
@marcphilipp said:
"We cannot use the M2 release Jenkins plugin to set these variables for us because it is not included in the free plan."
I asked if there is a way to persuade CloudBees to have this Artifactory Release in Jenkins.
@stephenc said 
"I can see about if we can install the plugin for you if you really need it. Shouldn't be an issue, but not my call"

@dsaff 
So if we had it, then you could have a more simple work without typing commands like mentioned in `doc/building-junit.txt`. That file is just info what Jenkins will do with the settings in pure UI release mgmt.

Just see this video which demonstrates how the release process would be:

http://www.youtube.com/watch?v=7IJVG7asfPE

I am going to add `-Dtag=4.12` to the doc, but using the Jenkins plugin it would be as easy as using an UI.

Sorry for the long comment.