[JENKINS-25753] BuildResultTrigger doesn't trigger build

Victor Engmark created issue - 2014-11-24 09:44

Victor Engmark made changes - 2014-11-24 09:44

Description

Original: The job with the following configuration never triggers, even after an unstable acceptance_test run:

  <triggers>
    <org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17">
      <spec>0 5 * * *</spec>
      <combinedJobs>false</combinedJobs>
      <jobsInfo>
        <org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
          <jobNames>acceptance_test</jobNames>
          <checkedResults>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>SUCCESS</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>UNSTABLE</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
          </checkedResults>
        </org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
      </jobsInfo>
    </org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger>
  </triggers>

New: The job with the following configuration never triggers, even after an unstable acceptance_test run:

  <triggers>
    <org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17">
      <spec>0 5 * * *</spec>
      <combinedJobs>false</combinedJobs>
      <jobsInfo>
        <org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
          <jobNames>acceptance_test</jobNames>
          <checkedResults>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>SUCCESS</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>UNSTABLE</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
          </checkedResults>
        </org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
      </jobsInfo>
    </org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger>
  </triggers>

Similar issue: https://issues.jenkins-ci.org/browse/JENKINS-12427

Alexey Larsky added a comment - 2015-04-28 14:57 - edited

The simular situation polling schedule "* * * * *" works fine, but something like "0 9 * * *" with minutes and/or hours skips all checks:

Polling started on Apr 28, 2015 5:50:58 PM
Polling for the job Test_BuildResultTrigger
Recording context. Check changes in next poll.

Polling complete. Took 0 ms.
No changes.

instead

Polling started on Apr 28, 2015 5:56:58 PM
Polling for the job Test_BuildResultTrigger
Checking changes for job Test_BuildResultTrigger_1.
There are no new builds for the job Test_BuildResultTrigger_1.
Checking changes for job Test_BuildResultTrigger_2.
There are no new builds for the job Test_BuildResultTrigger_2.
Checking changes for job Test_BuildResultTrigger_3.
There are no new builds for the job Test_BuildResultTrigger_3.

Polling complete. Took 1 ms.
No changes.

Alexey Larsky added a comment - 2015-04-28 14:57 - edited The simular situation polling schedule "* * * * *" works fine, but something like "0 9 * * *" with minutes and/or hours skips all checks: Polling started on Apr 28, 2015 5:50:58 PM Polling for the job Test_BuildResultTrigger Recording context. Check changes in next poll. Polling complete. Took 0 ms. No changes. instead Polling started on Apr 28, 2015 5:56:58 PM Polling for the job Test_BuildResultTrigger Checking changes for job Test_BuildResultTrigger_1. There are no new builds for the job Test_BuildResultTrigger_1. Checking changes for job Test_BuildResultTrigger_2. There are no new builds for the job Test_BuildResultTrigger_2. Checking changes for job Test_BuildResultTrigger_3. There are no new builds for the job Test_BuildResultTrigger_3. Polling complete. Took 1 ms. No changes.

Alexandru Gheorghe added a comment - 2015-05-29 15:40

Same with H 17 * * 5, the upstream job (makes the upstream/downstream automatically when i try to monitor a job) has its state as SUCCESS however after poll it says "No changes" and just stays like that. It should trigger upon "SUCCESS" and my option to "Combine all job info" is disabled.

Alexandru Gheorghe added a comment - 2015-05-29 15:40 Same with H 17 * * 5 , the upstream job (makes the upstream/downstream automatically when i try to monitor a job) has its state as SUCCESS however after poll it says "No changes" and just stays like that. It should trigger upon "SUCCESS" and my option to "Combine all job info" is disabled.

Alexandru Gheorghe made changes - 2015-05-29 15:41

Link

New: This issue is related to ~~JENKINS-12427~~ [ ~~JENKINS-12427~~ ]

Alexandru Gheorghe made changes - 2015-05-29 15:41

Component/s

New: buildresulttrigger [ 15924 ]

Alexandru Gheorghe made changes - 2015-06-02 07:28

Description

Original: The job with the following configuration never triggers, even after an unstable acceptance_test run:

  <triggers>
    <org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17">
      <spec>0 5 * * *</spec>
      <combinedJobs>false</combinedJobs>
      <jobsInfo>
        <org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
          <jobNames>acceptance_test</jobNames>
          <checkedResults>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>SUCCESS</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>UNSTABLE</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
          </checkedResults>
        </org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
      </jobsInfo>
    </org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger>
  </triggers>

Similar issue: https://issues.jenkins-ci.org/browse/JENKINS-12427

New: The job with the following configuration never triggers, even after an unstable acceptance_test run:

{noformat}
  <triggers>
    <org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17">
      <spec>0 5 * * *</spec>
      <combinedJobs>false</combinedJobs>
      <jobsInfo>
        <org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
          <jobNames>acceptance_test</jobNames>
          <checkedResults>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>SUCCESS</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
            <org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
              <checked>UNSTABLE</checked>
            </org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult>
          </checkedResults>
        </org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo>
      </jobsInfo>
    </org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger>
  </triggers>
{noformat}

See related ticket(s) for similarity.

Jack T added a comment - 2016-01-04 14:26

I am running into the same issue. "* * * * *" combined with SUCCESS works but changing the cron value to something that has minutes or hours caused the job to never get triggered.

Anyone come up with a work around to the BuildResultTrigger plugin or another method to schedule executed based on the success of another job?

Thanks.

Jack T added a comment - 2016-01-04 14:26 I am running into the same issue. "* * * * *" combined with SUCCESS works but changing the cron value to something that has minutes or hours caused the job to never get triggered. Anyone come up with a work around to the BuildResultTrigger plugin or another method to schedule executed based on the success of another job? Thanks.

Andreas Messer added a comment - 2016-04-27 07:16

I can confirm this. Job is configured to poll once in the evening another job and it doesn't work. The following time setting does not work "0 18 * * 5" while "*/5 7-18 * * 5" does work after some poll (The log has no meaningfull output on the first poll)

I had look into the source code an I think this is a problem of the x-trigger-lib: It seems that the "context" member variable is marked as "transient". That means on serialization of the Trigger it will be discarded. I dont know much about java and jenkins but maybe the Trigger objects will be saved to disk if not used frequently. I think they're also serialized when beeing executed on another machine. If that happens, the previous state of the polled jobs is lost and the Trigger starts from a new state. This theory would alos explain the empty BuildResultTrigger log (No polled jobs seen).

Andreas Messer added a comment - 2016-04-27 07:16 I can confirm this. Job is configured to poll once in the evening another job and it doesn't work. The following time setting does not work "0 18 * * 5" while "*/5 7-18 * * 5" does work after some poll (The log has no meaningfull output on the first poll) I had look into the source code an I think this is a problem of the x-trigger-lib: It seems that the "context" member variable is marked as "transient". That means on serialization of the Trigger it will be discarded. I dont know much about java and jenkins but maybe the Trigger objects will be saved to disk if not used frequently. I think they're also serialized when beeing executed on another machine. If that happens, the previous state of the polled jobs is lost and the Trigger starts from a new state. This theory would alos explain the empty BuildResultTrigger log (No polled jobs seen).

R. Tyler Croy made changes - 2016-07-25 23:51

Workflow

Original: JNJira [ 159731 ]

New: JNJira + In-Review [ 180101 ]

Jenkins

Details

Description

Attachments

Issue Links

Activity

Collapse comment: Alexey Larsky added a comment - 2015-04-28 14:57, Edited by Alexey Larsky - 2015-04-28 15:05

Expand comment: Alexey Larsky added a comment - 2015-04-28 14:57, Edited by Alexey Larsky - 2015-04-28 15:05

Collapse comment: Alexandru Gheorghe added a comment - 2015-05-29 15:40

Expand comment: Alexandru Gheorghe added a comment - 2015-05-29 15:40

Collapse comment: Jack T added a comment - 2016-01-04 14:26

Expand comment: Jack T added a comment - 2016-01-04 14:26

Collapse comment: Andreas Messer added a comment - 2016-04-27 07:16

Expand comment: Andreas Messer added a comment - 2016-04-27 07:16

People

Dates