[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
S P created JENKINS-12427:
-----------------------------

             Summary: 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
    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
         Attachments: TEST-Trigger.config.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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S P updated JENKINS-12427:
--------------------------

    Component/s: buildresulttrigger
   

> 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
>         Attachments: TEST-Trigger.config.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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

gbois reassigned JENKINS-12427:
-------------------------------

    Assignee: gbois
   

> 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.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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

gbois resolved JENKINS-12427.
-----------------------------

    Resolution: Not A Defect

According the config files, there are no build results to check. Therefore, you have to click on the button 'Add a build result' in the build-result section.

Do not hesitate to reopen the issue if it doesn't fix the issue.
               

> 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.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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159631#comment-159631 ]

S P commented on JENKINS-12427:
-------------------------------

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

               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S P updated JENKINS-12427:
--------------------------

    Attachment: TEST-TRY.config-2.xml

updated to include more build results
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S P reopened JENKINS-12427:
---------------------------

   

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159638#comment-159638 ]

gbois commented on JENKINS-12427:
---------------------------------

OK,
Be careful for your cron expression

'* * * * *' or '*/1 * * * *' means each minute

'1 * * * *' means each hour at 59

Could you check your conf?
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159640#comment-159640 ]

S P commented on JENKINS-12427:
-------------------------------

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.
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159811#comment-159811 ]

gbois commented on JENKINS-12427:
---------------------------------

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?
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159877#comment-159877 ]

gbois commented on JENKINS-12427:
---------------------------------

Any update?
Thanks
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159977#comment-159977 ]

gbois commented on JENKINS-12427:
---------------------------------

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.
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160264#comment-160264 ]

gbois commented on JENKINS-12427:
---------------------------------

Does it suit you?
               

> 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

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S P resolved JENKINS-12427.
---------------------------

    Resolution: Cannot Reproduce

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
               

> 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