One pain point we've been dealing with in Go is that you have to explicitly configure all your email notifications. This may be nice in some scenarios but for us its a real pain. We want to recieve all notifications for every pipeline and every stage regardless of who commited. So anytime we add a new pipeline the developers have to go in an setup notifications for it and all the stages. It would really be great if we could just check a checkbox that allows a user to get *all* notifications period so we dont have to keep going back in and configuring them individually.
Thanks!
m
Comments
4 comments
I would like to see this as well.
But, while I'm at it, we have a related requirement - we want to have notifications for certain events sent to mailing lists or to users who don't log in to Go - preferabley to be done by the pipeline admin(s) for the pipeline(s) in question, not by someone logging in and making the mailing list his email address in his profile. Since users authenticate against an LDAP, bogus users won't work as well (also adding users in the auth file requires access to the system we don't have).
/Steve Elkind
Yeah, actually, thats even better. +1
I should mention the resulting list of notification emails for a specific event would be the union of the two methods, neither overriding the other
I would also find a more powerful notification process helpful. We have multiple stakeholders (some Go users asome not) who need to be notified as a group at key events (e.g. at deployment to test environments and of course at releases. Communication/notificaiton is a very key process in agile software development and therefore I think it makes a lot of sense to see how Go can support this in a smooth way. We also use LDAP so making dummy accounts is not really a feasible approach.
How do you guys at Thoughtworks handle this kind of notifications?
Please sign in to leave a comment.