|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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.
Firstly, do you really want the email stuff in the README.md?
Secondly, this is something that should really be considered more Jenkins specific...
So as a result you should handle it with the .jenkins/ directory in SCM and just add the Mailer's XML descriptor... or better yet define a more literate style descriptor parser for mailing config.
You may want to turn off/ignore emails from specific branches, all that points to the .jenkins folder handling logic (i.e. branch profiles, etc)
There is also the question of whether you should be storing email addresses in SCM... given that you might have to re-activate an old branch which triggers emails to people that are no longer working on the project, etc... (but that is not a new question)
I would point to the https://github.com/jenkinsci/literate-plugin/blob/master/src/main/java/org/cloudbees/literate/jenkins/publishers/Agent.java class as the extension point where this would be easiest addressed.
An EmailerAgent could parse a simple plain text format descriptor and construct the EmailPublisher instance to be used by each branch.... that would give the nice plain text support and allow people to disable the agent for e.g. pull request branches, etc
If you don't create a custom format (e.g. like what I did with the two example Agents for JUnit and artifact archiving) then the default XML agent will pick up and XML file for emailer publisher config if present...
So the literate plugin does actually have email feature right now... you just have to write it in XML