Loading ...Keep fighting the voodoo
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?
- Build Configuration –> Agent Requirementse –> Add requirements for environment variable –> SHITTY_AGENT (condition = “does not exist”)
- Go to the shitty agent and add a system variable named SHITTY_AGENT
- Restart the build service:
- net stop “TeamCity Build Agent Service”
- net start “TeamCity Build Agent Service”
