|
||||||||||||
|
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-16014) losing build history in configuration matrix jobs
michael.serisier+jenkinsj...@gmail.com (JIRA) Mon, 03 Dec 2012 06:04:48 -0800
- [JIRA] (JENKINS-16014) losin... michael.serisier+jenkinsj...@gmail.com (JIRA)
- [JIRA] (JENKINS-16014) ... michael.serisier+jenkinsj...@gmail.com (JIRA)
- [JIRA] (JENKINS-16014) ... michael.serisier+jenkinsj...@gmail.com (JIRA)
- [JIRA] (JENKINS-16014) ... michael.serisier+jenkinsj...@gmail.com (JIRA)
- [JIRA] (JENKINS-16014) ... blatinvill...@gmail.com (JIRA)
- [JIRA] (JENKINS-16014) ... aba...@java.net (JIRA)
Steps:
1. Unzip the zip file in <JENKINS_HOME>\jobs
2. Reload the Jenkins configuration
3. Click the project name
Observe: the build of the project are all listed, but the builds of the "default" configuration are not loaded. In some cases, the builds of the "default" configuration are even deleted at startup.
The default configuration is run on the master.
In my production system, the configuration axes involve proper slaves, not just the "default" configuration.