A Quantum Immortal

Good developers dislike voodoo, but sometimes all the good will can’t stop a dark spawn of evil. For example, one of our build machines always bluescreens when running a certain system test. Why? Probably some hardware/driver failure, we’ll look into that.

In the meantime, let’s just ensure the build agent doesn’t get these nasty builds, shall we?

1. Build Configuration –> Agent Requirementse –> Add requirements for environment variable –> SHITTY_AGENT (condition = “does not exist”)
2. Go to the shitty agent and add a system variable named SHITTY_AGENT
3. Restart the build service:
   1. net stop “TeamCity Build Agent Service”
   2. net start “TeamCity Build Agent Service”

Similar Posts:

• Requiring a minimum CPU benchmark in TeamCity
• Ouch, System process is locking my folders!
• Knuth and The City (TeamCity!)
• Some More on TeamCity
• Beware of Windows XP SP3 !!!

Related posts:

1. Requiring a minimum CPU benchmark in TeamCity
2. Ouch, System process is locking my folders!
3. Knuth and The City (TeamCity!)
4. Some More on TeamCity
5. 11 Tips for Beginner C# Developers