-
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
-
JENKINS-25753 BuildResultTrigger doesn't trigger build
- Open
-
JENKINS-14446 Getting 'ERROR - SEVERE - Polling error null' with builds using Matrix Tie Parent Plugin
- In Progress