-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Linux, 2.6.26-amd64
debian_version 5.0.6
Jenkins BuildResultTrigger Plug-in 0.4
Jenkins ver. 1.440
Jenkins with the buildResultTrigger plugin is unable to trigger a job
Two jobs are setup,
1. TEST-TRIGGER is a basic job that always passes
(from jenkins log)
INFO | jvm 2 | 2012/01/17 10:47:31 | 17/01/2012 10:47:31 AM hudson.model.Run run
INFO | jvm 2 | 2012/01/17 10:47:31 | INFO: TEST-Trigger #7 main build action completed: SUCCESS
2. TEST-TRY is a basic job configured to Monitor build results of TEST-Trigger. This job is able to run with success when trigger manually
(from jenkins log)
INFO | jvm 2 | 2012/01/17 10:48:51 | 17/01/2012 10:48:51 AM hudson.model.Run run
INFO | jvm 2 | 2012/01/17 10:48:51 | INFO: TEST-TRY #2 main build action completed: SUCCESS
However, a success result from TEST-TRIGGER does not fire the TEST-TRY job.
Both jobs configurations are attached
- is related to
-
-
- Open
-
-
-
- In Progress
-
[JENKINS-12427] BuildResultTrigger Plug-in not triggering job
S P
added a comment - OK, that is weird. The drop downs were selected when I opened the job. I've added more build results and they are visible in the config but still no firing of the job. I've added a updated config file. TEST-TRY.config-2.xml
S P
added a comment - OK, that is weird. The drop downs were selected when I opened the job. I've added more build results and they are visible in the config but still no firing of the job. I've added a updated config file. TEST-TRY.config-2.xml 
Gregory Boissinot
added a comment - OK,
Be careful for your cron expression
'* * * * ' or '/1 * * * *' means each minute
'1 * * * *' means each hour at 59
Could you check your conf?
Gregory Boissinot
added a comment - OK,
Be careful for your cron expression
'* * * * ' or ' /1 * * * *' means each minute
'1 * * * *' means each hour at 59
Could you check your conf? S P
added a comment - yep, thanks for the reminder, however the cron is fine in this case. I changed the job config 9 days ago, and triggered a fresh run of the watched job.
S P
added a comment - yep, thanks for the reminder, however the cron is fine in this case. I changed the job config 9 days ago, and triggered a fresh run of the watched job. Gregory Boissinot
added a comment - I'm afraid I can't reproduce your problem.
It's OK in my environment.
Could you try in your side to isolate the problem with a simple case/job and with a cron to 1 minute?
Gregory Boissinot
added a comment - I'm afraid I can't reproduce your problem.
It's OK in my environment.
Could you try in your side to isolate the problem with a simple case/job and with a cron to 1 minute? Gregory Boissinot
added a comment - Any update?
Thanks S P
added a comment - Sorry for the delay.
Yes I ran it again with a cron of 1 min, and no change.
The jobs don't actually do anything, by that I mean they don't have any code they compile or tests they run, they are just empty jobs but they do finish with success. Do you think that could be the issue?
Are you running the same job configs?
We do have a bunch of other plugins in our jenkins. I wonder if something is interfering.
S P
added a comment - Sorry for the delay.
Yes I ran it again with a cron of 1 min, and no change.
The jobs don't actually do anything, by that I mean they don't have any code they compile or tests they run, they are just empty jobs but they do finish with success. Do you think that could be the issue?
Are you running the same job configs?
We do have a bunch of other plugins in our jenkins. I wonder if something is interfering.
Gregory Boissinot
added a comment - According your configuration files, you have to follow these rules:
- You can't monitor the job itself
- You have to add at least one result (SUCCESS, ....)
And with these constraints, it's OK in my environment.
Gregory Boissinot
added a comment - According your configuration files, you have to follow these rules:
You can't monitor the job itself
You have to add at least one result (SUCCESS, ....)
And with these constraints, it's OK in my environment. Gregory Boissinot
added a comment - Does it suit you? S P
added a comment - Yes, those rules you mention are fine for what I'm trying to do.
I can't figure out why it isn't working for us and I don't know where else to look.
I'll close the issue and try to work on it again another day.
Thanks for your time
S P
added a comment - Yes, those rules you mention are fine for what I'm trying to do.
I can't figure out why it isn't working for us and I don't know where else to look.
I'll close the issue and try to work on it again another day.
Thanks for your time 
updated to include more build results