-
Bug
-
Resolution: Duplicate
-
Blocker
-
Windows Server 2008 SP2
I have several jobs set to use a configuration matrix. Since I upgraded to 1.492, it looks like builds are lost after each Jenkins restart. This happens for some jobs only.
I have already had problems loading the old builds in such jobs in the past (after the changes made to improve Jenklins startup times around 1.47x), but at least the build folders weren't removed from the disk, so downgrading fixed my issues.
Here is a better description of the jobs that lose their history:
MYJOB: matrix configuration of "windows" and "linux"
runs on: master (which is also the machine used for the "windows" configuration)
After a Jenkins restart (Jenkins is running as a service), all folders inside of \Jenkins\jobs\MYJOB\configurations\axis-os\windows\builds are moved.
The folders in \Jenkins\jobs\MYJOB\builds are not affected
The only plugin used by this job is https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin, but it is used in jobs that are not affected by this weird behaviour.
I cannot find any errors in the logs, and I'm wondering where to start to provide any interesting information to understand the problem.
Is anyone else experiencing something like this?
- duplicates
-
-
- Resolved
-
[JENKINS-16014] losing build history in configuration matrix jobs
Michaël Serisier
created issue -
Michaël Serisier
made changes -
| Priority | Original: Critical [ 2 ] | New: Blocker [ 1 ] |
Michaël Serisier
added a comment - 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.
Michaël Serisier
added a comment - 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. Michaël Serisier
made changes -
| Attachment | New: 12E.zip [ 22912 ] |
Bertrand Latinville
added a comment - I'm facing a similar issue when adding configurations to existing matrix job.
Here is the details of the issue as reported on the mailing list.
I have made some changes in matrix jobs. I have added new configuration to a user defined axis.
The matrix job run properly and I could see that new configuration was build properly :
- The parent jobs console log says " newconfiguation completed with result SUCCESS"
I can go to the the new configuration web page, see the logs and the artifacts.
Looking at the matrix, the bullet corresponding to the new configuration is blue !
After some time ( less than 2 hours) the result from the build is lost.
The bullet corresponding to the new configuration is grey and indicates NOT RUN when I pass the mouse over it.
So I cannot click on the bullet to see the build.
If I go back to the parent job console, I can click on the "newconfiguation completed with result SUCCESS" link.
I get a web page, where everything is empty : no Build History, empty change log, no artifacts.
I run the job again . Can see the newconfiguration build. Some hours later , everything is gone again.
Looking on the master node , in /va/lib/jenkins/jobs, I can see
/var/lib/jenkins/jobs/job_name/configurations/../axis-xxx/newconfiguration/
I this folder everything looks fine : "builds config.xml lastStable lastSuccessful"
In lastSuccessful I can see the log, the build.xml.
Cf this topic on the mailing list:
https://groups.google.com/forum/#!topic/jenkinsci-users/uBdlIp69uhQ
Bertrand Latinville
added a comment - I'm facing a similar issue when adding configurations to existing matrix job.
Here is the details of the issue as reported on the mailing list.
I have made some changes in matrix jobs. I have added new configuration to a user defined axis.
The matrix job run properly and I could see that new configuration was build properly :
The parent jobs console log says " newconfiguation completed with result SUCCESS"
I can go to the the new configuration web page, see the logs and the artifacts.
Looking at the matrix, the bullet corresponding to the new configuration is blue !
After some time ( less than 2 hours) the result from the build is lost.
The bullet corresponding to the new configuration is grey and indicates NOT RUN when I pass the mouse over it.
So I cannot click on the bullet to see the build.
If I go back to the parent job console, I can click on the "newconfiguation completed with result SUCCESS" link.
I get a web page, where everything is empty : no Build History, empty change log, no artifacts.
I run the job again . Can see the newconfiguration build. Some hours later , everything is gone again.
Looking on the master node , in /va/lib/jenkins/jobs, I can see
/var/lib/jenkins/jobs/job_name/configurations/../axis-xxx/newconfiguration/
I this folder everything looks fine : "builds config.xml lastStable lastSuccessful"
In lastSuccessful I can see the log, the build.xml.
Cf this topic on the mailing list:
https://groups.google.com/forum/#!topic/jenkinsci-users/uBdlIp69uhQ | Link |
New:
This issue duplicates |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Workflow | Original: JNJira [ 146816 ] | New: JNJira + In-Review [ 192095 ] |
I can reproduce the problem on a new (clean!) installation, old builds are not loaded after a restart, although my folders aren't always deleted at startup.
I'll include a simple job configuration file so you can reproduce it.