Details
-
Story
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
-
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
Issue Links
- is blocked by
-
-
- Closed
-
- relates to
-
JENKINS-39860 Messages column in blue ocean should display if there are more commits
-
- Closed
-
-
-
- Closed
-
Activity
jamesdumay it's what jglick referenced in Stapler 1.250 => 1.252 upgrade notes in https://github.com/jenkinsci/jenkins/pull/2956
michaelneale Bumped up the priority of this one because today its hard to work with our ATH. Consider this a feature for our team.