|
||||||||
|
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-14474) Multi-config... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)
- [JIRA] (JENKINS-14474) Multi-c... [email protected] (JIRA)

I think that there are actually two bugs. I have now downgraded to 1.472 as you suggested. The behaviour I see is the same as that of the 1.475 release candidate that I was trying before (see my earlier comment for details). So I agree that the really serious bug does not seem to be present in that version.
But I am still getting null pointer exceptions when Jenkins tries to load my old multi-configuration jobs, which I created in my old Jenkins system. I can live with this, because I haven't got many of those jobs, and I can re-create them manually.