email notifier and build dependencies
If we have build A that depends on build B and a user commits changes to build B that triggers a build and it succeeds, but later in the build chain build A fails - does the user that committed changes to build B get notified. I mean build A has no changes except for the fact that it uses a "snapshot artifact" from build B that causes it to fail. We are using TeamCity Enterprise 2017.2.2 (build 50909)
Please sign in to leave a comment.
Hi JT,
I'm afraid that notifications are configured at the build level, and can't really take into account dependencies. A build might fail because of its dependencies, but might as well fail for multiple other reasons, including even other artifacts, and TeamCity doesn't have a way to know it, so notifying all of its dependencies committers could produce large amounts of noise in large, complex builds.
The changes from dependencies can be made viewable for the latter builds in their VCS settings, so the best option would be to set the notifications for A.