• Type: Improvement
• Resolution: Won't Do
• Priority: Minor
• Component/s: email-ext-plugin
• Labels:

  • user-experience
• Environment:

  Jenkins LTS 2.32.3
  Email Extension Plugin 2.57
  Pipeline 2.5

[JENKINS-42644] Allow pipeline jobs to be watched

Paul LeTang created issue - 2017-03-09 22:09

Paul LeTang made changes - 2017-03-09 22:13

Description

Original: The Editable Email Notification Post-build Action lets uses subscribe to email triggers on that job. This is a more elegant solution than making a change to a Jenkinsfile whenever I want to change the email list for a build. Can we get a way for users to configure which jobs they want to watch without needing to touch sourcecode?

New: The Editable Email Notification Post-build Action lets uses subscribe to email triggers on that job, but this only seems to be exposed to freestyle jobs. This is a more elegant solution than making a change to a Jenkinsfile whenever I want to change the email list for a build. Can we get a way for users to configure which jobs they want to watch without needing to touch sourcecode?

Paul LeTang made changes - 2017-03-09 22:23

Description

Original: The Editable Email Notification Post-build Action lets uses subscribe to email triggers on that job, but this only seems to be exposed to freestyle jobs. This is a more elegant solution than making a change to a Jenkinsfile whenever I want to change the email list for a build. Can we get a way for users to configure which jobs they want to watch without needing to touch sourcecode?

New: The Editable Email Notification Post-build Action lets uses subscribe to email triggers on that job, but this only seems to be exposed to freestyle jobs. This is a more elegant solution than making a change to a Jenkinsfile whenever I want to change the email list for a build. Can we get a way for users to configure which pipeline jobs they want to watch without needing to touch sourcecode?

Collapse comment: Daniel Hoerner added a comment - 2017-04-04 14:50

Daniel Hoerner added a comment - 2017-04-04 14:50

Is there already an approximate time when this feature will be implemented?

Expand comment: Daniel Hoerner added a comment - 2017-04-04 14:50

Daniel Hoerner added a comment - 2017-04-04 14:50 Is there already an approximate time when this feature will be implemented?

Collapse comment: David van Laatum added a comment - 2017-04-05 05:06

David van Laatum added a comment - 2017-04-05 05:06

I have no plans to do this at this stage but will accept a pull request

Expand comment: David van Laatum added a comment - 2017-04-05 05:06

David van Laatum added a comment - 2017-04-05 05:06 I have no plans to do this at this stage but will accept a pull request

Collapse comment: Andrew C added a comment - 2017-12-13 22:28

Andrew C added a comment - 2017-12-13 22:28

@davidvanlaatum not having pipeline support for triggers continues to be an impediment – has your opinion at all changed on this?

Thank you.

Expand comment: Andrew C added a comment - 2017-12-13 22:28

Andrew C added a comment - 2017-12-13 22:28 @ davidvanlaatum  not having pipeline support for triggers continues to be an impediment – has your opinion at all changed on this? Thank you.

Andrew Bayer made changes - 2018-02-26 21:29

Component/s

Original: pipeline [ 21692 ]

Basil Crow made changes - 2020-10-27 02:24

Assignee

Original: David van Laatum [ davidvanlaatum ]

Collapse comment: Alex Earl added a comment - 2024-11-13 02:06

Alex Earl added a comment - 2024-11-13 02:06

The same mechanisms that are used for free style jobs are not available for pipeline jobs. 

Expand comment: Alex Earl added a comment - 2024-11-13 02:06

Alex Earl added a comment - 2024-11-13 02:06 The same mechanisms that are used for free style jobs are not available for pipeline jobs. 

Alex Earl made changes - 2024-11-13 02:06

Resolution		New: Won't Do [ 10001 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]