New jenkins versions are released very often (and often break). I would propose the long-term releases to be added.
Going to need version numbers for that proposal.
So 1.565 is the LTS, and you're proposing a downgrade. Okay.
There is no mention of a "1.565.3" at: http://mirrors.jenkins-ci.org/war/ I can do you 1.565?
@Chainsaw: I guess Tomas is talking about this here http://jenkins-ci.org/changelog-stable http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war We can solve that using two slots for jenkins-bin (:0 and :lts), blocking each other. So we can avoid version numbers on the war-file.
Looks like a packaging nightmare, a "latest" moving target. Is upstream not willing to do something more suitable?
It's also available here (sorry just took the link from the main page): http://mirrors.jenkins-ci.org/war-stable/1.565.3/jenkins.war
Yes, there are two types of releases, the newests being at: http://mirrors.jenkins-ci.org/war/ (http://jenkins-ci.org/changelog) and the "stable" ones at: http://mirrors.jenkins-ci.org/war-stable/ (http://jenkins-ci.org/changelog-stable)
*jenkins-bin-1.565.3 (27 Oct 2014) *jenkins-bin-1.586 (27 Oct 2014) 27 Oct 2014; Manuel Rüger <mrueg@gentoo.org> +jenkins-bin-1.565.3.ebuild, +jenkins-bin-1.586.ebuild, jenkins-bin-1.585.ebuild: Version bump. Add lts slot and make both slots block each other. Fixes bug #526214. In tree, hope that works.
Tested, works, thanks.