-
Story
-
Resolution: Fixed
-
Major
-
-
1.0, Blue Ocean - 1.1-beta2
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.
- is blocked by
-
-
- Closed
-
- relates to
-
JENKINS-39860 Messages column in blue ocean should display if there are more commits
-
- Closed
-
-
-
- Closed
-
[JENKINS-40979] Developer would like to see why the Pipeline has been triggered
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?
sophistifunk 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
michaelneale Vivek mentioned that he has to go back to classic when analysing ATH failures to get this info.
michaelneale I keep running into this problem when trying to differentiate runs of the ATH.
michaelneale Bumped up the priority of this one because today its hard to work with our ATH. Consider this a feature for our team.
jamesdumay it's what jglick referenced in Stapler 1.250 => 1.252 upgrade notes in https://github.com/jenkinsci/jenkins/pull/2956
jamesdumay need anything else from my end?