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

As I wrote to you, I had the same issues like yours and I downgraded to 1.472, only then everything back to normal (I was able to see "multi-configuration" jobs.
I recommended to you to actually copy the jenkins.war (1.472) and not to use the Jenkins downgrade option.
This is what I did:
1. Stop Jenkins service.
2. Copy (from backup) the jenkins.war (1.472) to Jenkins home folder (c:\Jenkins).
3. Start Jenkins service.
After you downgrade to 1.472, try to create a new "multi-configuration" job and see (after restart Jenkins) if the job staying stable. if its working, try to copy the config.xml from your old "multi-configuration" job to the new "multi-configuration" job.
In any case, this bug must be solved ASAP!