Hi there,
I had a very similar issue recently with a Mac master (and no slaves),
where one of the axis names was changed from "FOO" to "Foo", which
caused problems, because Jenkins found the already-existing "axis-FOO"
directory, but this caused problems as it didn't match "Foo" exactly.
Can you check that the axis names are matching the directory names used
everywhere?
Chris
On 23/11/2012 10:35, B.Latinville wrote:
Hello,
I'm using Jenkins 1.487 with matrix jobs. Debian master, linux & windows
slaves.
I've just 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.
Could not understand why this does not appear in jenkins.
Any Idea why the new build are lost ? This is really annoying. I've
faced this issue on several jobs.
I did not the the problem before has someone else seen this issue ?
Thanks.
Bertrand.
