Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12427

BuildResultTrigger Plug-in not triggering job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • buildresult-trigger-plugin, buildresulttrigger
    • 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

        1. TEST-Trigger.config.xml
          0.9 kB
        2. TEST-TRY.config.xml
          1 kB
        3. TEST-TRY.config-2.xml
          2 kB

          [JENKINS-12427] BuildResultTrigger Plug-in not triggering job

          S P created issue -
          S P made changes -
          Component/s New: buildresulttrigger [ 15924 ]
          Gregory Boissinot made changes -
          Assignee New: Gregory Boissinot [ gbois ]

          Gregory Boissinot added a comment -

          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.

          Gregory Boissinot added a comment - 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.
          Gregory Boissinot made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          S P added a comment -

          updated to include more build results

          S P added a comment - updated to include more build results
          S P made changes -
          Attachment New: TEST-TRY.config-2.xml [ 21572 ]

          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
          S P made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          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?

            gbois Gregory Boissinot
            sp S P
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: