|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Not a problem, I am glad you like the idea. It’s just one of those idea’s you find being the defacto (part time) Admin for a box with jobs copied over from an old Hudson Server and people constantly be asked by users to be added and or removed from them from groups.
One of the things that I think would go well with the, especially if you are making a new configuration page would be to have the ability to view and possibly edit existing jobs that have the email-ext enable.
I actually wrote a simple bash script to read and parse all the config.xml so it would tell me what job had what email-ext triggers enabled and who the triggered e-mails are going to. So it’s like a quick overview of all the triggers. This could be taken to the next step where one could look at a tabularized data of jobs and templates and edit them on one page without have to go into the job itself.