[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1.0, up next Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1.0, release candidates 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1.0 , release candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1.0 , 1.0-rc1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1.0 , 1.0-rc1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered Michael Neale I keep running into this problem when trying to differentiate runs of the ATH. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1. 1 0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: 1. 0 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: up next 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: panthalassa up next Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: up next panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered Michael Neale Vivek mentioned that he has to go back to classic when analysing ATH failures to get this info. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: panthalassa release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40979
Developer would like to see why the Pipeline has been triggered
Change By:
James Dumay
*Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message cell should be the trigger reason. !message.png|thumbnail! *Notes*Would be good to do in conjunction with JENKINS-39860. *Technical details*There should be an action on each run like:{code}{ "_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"}{code}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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40979
Developer would like to see why the Pipeline has been triggered
Change By:
James Dumay
Comment:
There should be an action on each run like:{code}{ "_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"}{code}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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay edited a comment on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
There should be an action on each run like:{code}{ "_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"}{code}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 cause description to be fixed in JENKINS-41736.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay edited a comment on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
There should be an action on each run like:{code}{ "_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"}{code}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 cause to be fixed in JENKINS-41736.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
James Dumay commented on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title
Michael Neale commented on JENKINS-40979
Re: Developer would like to see why the Pipeline has been triggered
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
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message cell should be the trigger reason. !message.png|thumbnail!*Notes*Would be good to do in conjunction with JENKINS-39860. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Michael Neale Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: panthalassa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Michael Neale Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Brody Maclean Michael Neale Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message column cell should be the trigger reason. !message.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *Scope** We want to show in this area the reason the run was triggered e.g. "Manual run by John" !Aborted.png|thumbnail! !upload-3.png|thumbnail! * If there is no "commit message" then the Message column should be the trigger reason. !message.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay edited a comment on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered ! blueocean 2017-02-06 09-30-21 message .png|thumbnail! 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? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Attachment: message.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered ! blueocean 2017-02-06 09-30-21.png|thumbnail! 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? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay edited a comment on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered ! blueocean 2017-02-06 09-30-21.png|thumbnail! 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? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Attachment: blueocean 2017-02-06 09-30-21.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Attachment: blueocean 2017-02-06 09-30-21.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title Brody Maclean commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered James Dumay need anything else from my end? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: Brody Maclean Attachment: Aborted.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay assigned an issue to Brody Maclean Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Assignee: Brody Maclean Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay Sprint: post-release iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title Michael Neale commented on JENKINS-40979 Re: Developer would like to see why the Pipeline has been triggered Vivek Pandey has also raised this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Change By: James Dumay *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 column should be the trigger reason. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40979) Developer would like to see why the Pipeline has been triggered
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40979 Developer would like to see why the Pipeline has been triggered Issue Type: Task Assignee: Unassigned Attachments: upload-3.png Components: blueocean-plugin Created: 2017/Jan/11 6:21 AM Priority: Minor Reporter: James Dumay Scope We want to show in this area the reason the run was triggered e.g. "Manual run by John" Add Comment
