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

Developer would like to see why the Pipeline has been triggered

    XMLWordPrintable

    Details

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

      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
            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: