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

Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want.

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Critical Critical
    • gerrit-trigger-plugin
    • None
    • 2.5.2
    • 2.31.0

      From time to time a job will get aborted currently gerrit-triggers treats them like fails and marks the patch -1 that isn't want I want I want it to leave it at zero but there doesn't seem to be a way to do this with the plug-in as is.

      Thanks
      Robert

          [JENKINS-14767] Add Reporting Values for Aborted jobs. Currently an aborted job uses the fail value not something everyone will want.

          Marco Leogrande added a comment -

          This is an interesting issue that happened to me when selecting `Build Current Patches Only`.

          If that checkbox is selected, when a new patchset is submitted for a commit the previous build is aborted, and Gerrit receives a -1 message for the outdated patchset. By adding a skip value for aborted builds I would be able to skip extra messages for outdated patchsets.

          Marco Leogrande added a comment - This is an interesting issue that happened to me when selecting `Build Current Patches Only`. If that checkbox is selected, when a new patchset is submitted for a commit the previous build is aborted, and Gerrit receives a -1 message for the outdated patchset. By adding a skip value for aborted builds I would be able to skip extra messages for outdated patchsets.

          Andy Wang added a comment -

          Yeah. The problem bothers me a lot. My gerrit triggered jobs are to set code-review -1 when build failed. Whenever I manually cancel a job it set the corresponding patch set to code-review -1, which is not what I should expected.
          I think it would be nice to add a skip value for aborted builds or just don't count canceled build as build failure.

          Andy Wang added a comment - Yeah. The problem bothers me a lot. My gerrit triggered jobs are to set code-review -1 when build failed. Whenever I manually cancel a job it set the corresponding patch set to code-review -1, which is not what I should expected. I think it would be nice to add a skip value for aborted builds or just don't count canceled build as build failure.

          Réda Housni Alaoui added a comment -

          Hi,

          I opened a pull request at https://github.com/jenkinsci/gerrit-trigger-plugin/pull/392

          Réda Housni Alaoui added a comment - Hi, I opened a pull request at  https://github.com/jenkinsci/gerrit-trigger-plugin/pull/392

          Kees Jongenburger added a comment -

          Hi,

           

          I opened a new pull request at  https://github.com/jenkinsci/gerrit-trigger-plugin/pull/413 looking forward to feedback

          Kees Jongenburger added a comment - Hi,   I opened a new pull request at   https://github.com/jenkinsci/gerrit-trigger-plugin/pull/413 looking forward to feedback

            rsandell rsandell
            rmiddle Robert Middleswarth
            Votes:
            8 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: