Hi Chris, The best practice approach is to have a single job per branch. This not only solves your problem but your trend reports will then have some form of linear code progression contained within them rather than jumping all over the shop.
So you are probably trying to fix something that isn't broken. As always though its code and there is probably a way this could work with the email-ext plugin and a pre-send that modifies the headers. /James On Friday, 25 October 2013 11:23:34 UTC-7, Chris Warren wrote: > > I've got a build job that will build any branch in a repository where new > changes are seen. I'd like to let the users specify lists of e-mail > recipients on a per-branch basis, so that the right people get news about > their branch's build. My first thought was that this could be done with a > config file in the source tree where users could edit their branch of the > file to have the addresses they want, but I would prefer it if I could keep > this configuration in Jenkins instead of in outside files. > > Is this a problem that other people run into, or am I trying to fix > something that isn't broken? > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
