One of the side effects of our increasingly popular TeamCity implementation is that our build agents are quickly running out of resources -- most notably disk space. To date we have about 115 distinct projects configured in TC (libraries, utilities, server-side apps, client-side apps, etc...) which at minimum have 2 build configurations each (a continuous build and a 'release candidate' build). Well done TC! :)
Pulling down a complete build workspace for each of these build runs, which for some projects also includes third-party .dll's and .so's to link against, starts to consume quite a bit of space.
I don't see anything in the agent properties that lists any real-time resource information about the box the agent is running in.
Granted, I can just throw more hardware at this problem but I rather be warned that a build agent is running out of space rather than act post-mortem after a build has failed due to disk-space.
I think a build agent property that specifies the current available disk-space would be very useful. That way a build agent can suddenly become "incompatible" with a build run and the build queue can take over and route the build to another, better suited, build agent.
This is of high priority to our org. so I'm also willing to do this as a plugin. Unfortunately, I don't see anything in the plugin API that might allow me to tack this on. Suggestions?