[JIRA] (JENKINS-43348) Option to use author instead of commiter in declarative pipeline

5 views
Skip to first unread message

andrew.bayer@gmail.com (JIRA)

unread,
Oct 1, 2018, 3:49:02 PM10/1/18
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
 
Jenkins / Bug JENKINS-43348
Option to use author instead of commiter in declarative pipeline
Change By: Andrew Bayer
Component/s: pipeline-model-definition-plugin
Component/s: blueocean-plugin
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

andrew.bayer@gmail.com (JIRA)

unread,
Oct 1, 2018, 3:49:03 PM10/1/18
to jenkinsc...@googlegroups.com

andrew.bayer@gmail.com (JIRA)

unread,
Oct 1, 2018, 3:49:03 PM10/1/18
to jenkinsc...@googlegroups.com
Andrew Bayer commented on Bug JENKINS-43348
 
Re: Option to use author instead of commiter in declarative pipeline

Seems like this may make sense to add as an option for Declarative - might actually end up doing it in git-plugin, though. We'll see.

andrew.bayer@gmail.com (JIRA)

unread,
Nov 15, 2018, 12:02:07 PM11/15/18
to jenkinsc...@googlegroups.com

brian.murrell@intel.com (JIRA)

unread,
Dec 3, 2019, 9:25:03 PM12/3/19
to jenkinsc...@googlegroups.com
Brian J Murrell commented on Improvement JENKINS-43348
 
Re: Option to use author instead of commiter in declarative pipeline

I have to agree completely that substituting the commiter for what should really be the patch author is really not very useful at all.  It doesn't make sense to e-mail the commiter when there is a problem with the patch.  It doesn't make sense for Blue Ocean to list the commiter as the person responsible for the change.

Is this issue anywhere near completion?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

junk@jdark.com (JIRA)

unread,
Jan 29, 2020, 6:37:03 AM1/29/20
to jenkinsc...@googlegroups.com

junk@jdark.com (JIRA)

unread,
Jan 29, 2020, 6:43:03 AM1/29/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages