Here is the bug on JIRA :
https://issues.jenkins-ci.org/browse/JENKINS-15799
Hopefully, it will be solved quickly. Vote for it it !
Moving to 1.492 solved problems on existing builds, but
I've not added new configurations in my jobs since the upgrade.
I'll try it to see the result.
If issue is still present I'll open a bug.
Any luck with 1.492? I'm seeing this with 1.490.
A.
On Wed, Nov 28, 2012 at 1:13 AM, B.Latinville wrote:
>
> I created a new job yesterday, copy from one existing matrix job.
> I run a single build, could see the build results.
> This morning it was not visible any more.
> I upgraded to 1.492, a
I created a new job yesterday, copy from one existing matrix job.
I run a single build, could see the build results.
This morning it was not visible any more.
I upgraded to 1.492, and my build result is back.
Rebooting jenkins did not solve the problem when it occurred.
Hopefully the upgrade will
Hi,
In my setup, the master does not execute the jobs.
I have slaves with label corresponding to the OS, and other labels (for
example, some related to tools that are installed). Also a "build" and
"test" label.
Here is the matrix job configuration, 2 axis :
- one "user defined axis", with se
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
Are you using labels to run these jobs on, or dynamic slaves.
As I have seen similar issue with pool of slaves on which my job runs, next
time when the job runs on different slave it looses the part that is slave
specific.
If not then can you please be more specific about your job configuration.
I
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 c
