[
https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159879#comment-159879
]
S P commented on JENKINS-12427:
-------------------------------
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.
> BuildResultTrigger Plug-in not triggering job
> ----------------------------------------------
>
> Key: JENKINS-12427
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12427
> Project: Jenkins
> Issue Type: Bug
> Components: buildresult-trigger, buildresulttrigger
> Affects Versions: current
> Environment: Linux, 2.6.26-amd64
> debian_version 5.0.6
> Jenkins BuildResultTrigger Plug-in 0.4
> Jenkins ver. 1.440
> Reporter: S P
> Assignee: gbois
> Attachments: TEST-Trigger.config.xml, TEST-TRY.config-2.xml,
> TEST-TRY.config.xml
>
>
> 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
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
