|
||||||||
|
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)

Yes. That's exactly what I did. And, indeed, I can create new multi-config jobs and they do stay stable, so I can use this version.
But I still have the other problem I mentioned: my old multi-config jobs that I created on my old system (Jenkins 1.441) and copied over to the new machine won't load. Jenkins gives a null-pointer exception when it tries to load them. So there is a separate bug to do with loading these old jobs. I should raise a separate bug report for that one, but at the moment I haven't done so, because the two issues seem to be so closely related. I thought it was better to wait and see what happens with this report first.