|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
For those of you who are more adventurous, here's a build that may or may not work, and may even make everything ten times worse:
https://dl.dropboxusercontent.com/u/29853/jenkins-1.600.JENKINS-27178.db.war
Based on this branch of 1.600 with fix: https://github.com/daniel-beck/jenkins/commits/JENKINS-27178, so you could read the diff to 1.600, know what was changed, and build it yourself.
This is completely untested other than making sure the builds no longer fail this particular way with env-inject installed. I did not roll back
JENKINS-26755, so this is a new state.If this issue turns out to be as serious as I fear, I'd prefer if one of the more regular core contributors would build a special build and upload to the Jenkins infra, but they're all offline right now. (Just to be sure I added the .db suffix to not have a naming collision with any other builds fixing this issue.)