Email notifications missing

Some of our users had defined personnal email notifications rules, but recently we have put in place system wide email notification practices using the notification rules of the "All Users" group

Notifs.bmp

Yesterday, a developper commited a couple of changes that "turned" maybe 25 build config from green to red.  But he received only 3 emails.

I looked at the log files on the server to try and learn a bit more about the email notification mechanism but learned nothing.  Was there a problem with the email server on our side or did the TeamCity server determined that this was going to be too many emails, and hence decided to send only a few?

Thanks

4 comments
Comment actions Permalink

Hi,

One clarification: did this user receive 3 "build_failed" email messages, or different ones?
What are the VCS username settings of the user? Is it possible that for some configurations build became red before his changes?


--
Maxim

0
Comment actions Permalink

He received 3 emails:

[TeamCity, FAILED] Build Telecom Trunk::SSAG2 Instrument FTB-400 Debug #45024.1882

Build Telecom Trunk::SSAG2 Instrument FTB-400 Debug #45024.1882 failed

Agent: VMMOBUILD23


Changes included (3 changes).

Change 45021 by micgre1 (1 file): Updated 2005 projects for commit 45020 DESCRIPTION: [...]

Change 45020 by micgre1 (62 files): Added a command to list Listeners into Provider console DESCRIPTION: [...]

Change 45024 by script (2 files): Updating version files for the loadbuild: PrePacketBlazer 85100G: FTB+IQS+PC 1.0.0.33 DESCRIPTION: [...]

[TeamCity, FAILED] Build Telecom Trunk::SSAG2 Unit Test .Net Builder #45024.2018

Build Telecom Trunk::SSAG2 Unit Test .Net Builder #45024.2018 failed (snapshot dependency build failed: 1)

Agent: VMMOBUILD23


Changes included (3 changes).

Change 45021 by micgre1 (1 file): Updated 2005 projects for commit 45020 DESCRIPTION: [...]

Change 45020 by micgre1 (62 files): Added a command to list Listeners into Provider console DESCRIPTION: [...]

Change 45024 by script (2 files): Updating version files for the loadbuild: PrePacketBlazer 85100G: FTB+IQS+PC 1.0.0.33 DESCRIPTION: [...]

[TeamCity, FAILED] Build Telecom Trunk::SSAG2 Target Firmware Release 8140 #45024.1851

Build Telecom Trunk::SSAG2 Target Firmware Release 8140 #45024.1851 failed ([Execution timeout] Failure)

Agent: VMMOBUILD26


Changes included (4 changes).

Change 45021 by micgre1 (1 file): Updated 2005 projects for commit 45020 DESCRIPTION: [...]

Change 45020 by micgre1 (62 files): Added a command to list Listeners into Provider console DESCRIPTION: [...]

Change 45024 by script (2 files): Updating version files for the loadbuild: PrePacketBlazer 85100G: FTB+IQS+PC 1.0.0.33 DESCRIPTION: [...]

Change 44954 by script (2 files): Updating version files for the loadbuild: PrePacketBlazer 85100G: FTB+IQS+PC 1.0.0.32 DESCRIPTION: [...]

His VCS settings are ... the same as everybody.  Subversion account only, same username as TC username as Windows domain username.  What settings are your reffering to?

And no, 99% of the configurations were green, and his changes only resulted in 25-30 turning to red.

Thanks

0
Comment actions Permalink

Hi,

I see, all three are "build failed" events.

> What settings are your reffering to?
Yes, I meant these settings. The issue is theoretically possible when a TeamCity user has several VCS accounts (e.g. git and svn), and just one of them is listed among VCS usernames. In this case TeamCity will only send a notification for configurations, in which it can detect his changes.

Do I understand correctly that in other configurations the failed build contained changes of "micgre1", just like in "SSAG2 Instrument FTB-400 Debug"? Are those builds marked as "failed to start"?
Are there any errors in the logs?


--
Maxim

0

Please sign in to leave a comment.