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

Developer would like to see why the Pipeline has been triggered

    Details

    • Similar Issues:
    • Sprint:
      1.0, Blue Ocean - 1.1-beta2

      Description

      Scope

      • We want to show in this area the reason the run was triggered e.g. "Manual run by John"

      • If there is no "commit message" then the Message cell should be the trigger reason.

      Notes
      Would be good to do in conjunction with JENKINS-39860.

      Technical details
      There should be an action on each run like:

      {
            "_class": "hudson.model.CauseAction",
            "_links": {
              "self": {
                "_class": "io.jenkins.blueocean.rest.hal.Link",
                "href": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/655/cause/"
              }
            },
            "causes": [
              {
                "_class": "jenkins.branch.BranchEventCause",
                "shortDescription": "Branch event"
              }
            ],
            "urlName": "cause"
          }
      

      You want to pick the first "cause" from that array. Every cause has a shortDescription.

      EDIT: I realise in this example that the cause is pretty meaningless to users and have asked for this particular description to be fixed in JENKINS-41736.

        Attachments

        1. Aborted.png
          Aborted.png
          134 kB
        2. message.png
          message.png
          131 kB
        3. upload-3.png
          upload-3.png
          180 kB

          Issue Links

            Activity

            Hide
            michaelneale Michael Neale added a comment -

            Vivek Pandey has also raised this.

            Show
            michaelneale Michael Neale added a comment - Vivek Pandey has also raised this.
            Hide
            brody Brody Maclean added a comment -

            James Dumay need anything else from my end?

            Show
            brody Brody Maclean added a comment - James Dumay need anything else from my end?
            Hide
            jamesdumay James Dumay added a comment - - edited

            When there is no "message" of what the build was for (e.g. was run with no changes) WDYT about showing the tigger reason there too?

            Show
            jamesdumay James Dumay added a comment - - edited When there is no "message" of what the build was for (e.g. was run with no changes) WDYT about showing the tigger reason there too?
            Hide
            michaelneale Michael Neale added a comment -

            Josh McDonald there should be enough data to show what the trigger was already in the row data. The text can be "Triggered by

            {reason}

            " type of thing

            Show
            michaelneale Michael Neale added a comment - Josh McDonald there should be enough data to show what the trigger was already in the row data. The text can be "Triggered by {reason} " type of thing
            Hide
            jamesdumay James Dumay added a comment -

            Michael Neale Vivek mentioned that he has to go back to classic when analysing ATH failures to get this info.

            Show
            jamesdumay James Dumay added a comment - Michael Neale Vivek mentioned that he has to go back to classic when analysing ATH failures to get this info.
            Hide
            jamesdumay James Dumay added a comment -

            Michael Neale I keep running into this problem when trying to differentiate runs of the ATH.

            Show
            jamesdumay James Dumay added a comment - Michael Neale I keep running into this problem when trying to differentiate runs of the ATH.
            Hide
            jamesdumay James Dumay added a comment -

            Michael Neale Bumped up the priority of this one because today its hard to work with our ATH. Consider this a feature for our team.

            Show
            jamesdumay James Dumay added a comment - Michael Neale Bumped up the priority of this one because today its hard to work with our ATH. Consider this a feature for our team.
            Hide
            jamesdumay James Dumay added a comment -

            Will be released in Blue Ocean 1.1

            Show
            jamesdumay James Dumay added a comment - Will be released in Blue Ocean 1.1
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Additional fix in Stapler has been integrated towards Jenkins 2.74

            Show
            oleg_nenashev Oleg Nenashev added a comment - Additional fix in Stapler has been integrated towards Jenkins 2.74
            Hide
            jamesdumay James Dumay added a comment -

            For this issue Oleg?

            Show
            jamesdumay James Dumay added a comment - For this issue Oleg?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            James Dumay it's what Jesse Glick referenced in Stapler 1.250 => 1.252 upgrade notes in https://github.com/jenkinsci/jenkins/pull/2956

            Show
            oleg_nenashev Oleg Nenashev added a comment - James Dumay it's what Jesse Glick referenced in Stapler 1.250 => 1.252 upgrade notes in https://github.com/jenkinsci/jenkins/pull/2956

              People

              • Assignee:
                jamesdumay James Dumay
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: