|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-9142) "Add Build Ste... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... [email protected] (JIRA)

I am using Jenkins own DB for security, with project-specific matrix permissions. During job configuration (for new or existing jobs), the add build step failed for all options, OSX/Chrome19.0.1084.56 and OSX/Firefox12.0 (about 270 yui "expected declaration but found '*' per page load in the FF error logs). I disabled the "Prevent Cross Site Request Forgery exploits" property in the Jenkins configuration (I had the crumb algo enabled as well), and the add build step started working again.