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

Information on what triggered a retry by Naginator

    XMLWordPrintable

Details

    Description

      A build shows the reason it got triggered, when hovering with the mouse. (example attached below)
      The retry always shows here "Re-scheduled after Failure".

      It would be nice to see here, what actually caused it.

      • "Re-scheduled due to matching RE in console"
      • "Re-scheduled by <USER-X>"
      • Re-scheduled after Failure"
      • <other possibilities ?>

      Currently I know of no way to tell, if a user clicked "Retry" or Naginator got triggered, because it was configured to do so (on RE match)

      Attachments

        Activity

          martinjost Martin Jost created issue -
          ndeloof Nicolas De Loof made changes -
          Field Original Value New Value
          Assignee Nicolas De Loof [ ndeloof ]

          People

            Unassigned Unassigned
            martinjost Martin Jost
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: