![]() For each pool TeamCity displays the status of its build agents. To view the agents alphabetically, uncheck the Group by agent pool box. The Connected and Disconnected tabs display the agents by Agent pool (default). The number of tabs on the page may differ depending on your agent setup. The Agents page of the TeamCity web UI provides the comprehensive information on the TeamCity agents. Might allow me to tack this on.Build Agents Configuration and Maintenance Viewing TeamCity Agents Details Unfortunately, I don't see anything in the plugin API that so I'm also willing to do this asĪ plugin. Over and route the build to another, better suited, build agent. That way a build agent can suddenlyīecome "incompatible" with a build run and the build queue can take I think a build agent property that specifies the current availableĭisk-space would be very useful. Post-mortem after a build has failed due to disk-space. Granted, I can just throw more hardware at this problem but I ratherīe warned that a build agent is running out of space rather than act Resource information about the box the agent is running in. I don't see anything in the agent properties that lists any real-time Link against, starts to consume quite a bit of space. Which for some projects also includes third-party. ![]() Pulling down a complete build workspace for each of these build runs, To date we have about 115ĭistinct projects configured in TC (libraries, utilities, server-sideĪpps, client-side apps, etc.) which at minimum have 2 buildĬonfigurations each (a continuous build and a 'release candidate' Implementation is that our build agents are quickly running out of One of the side effects of our increasingly popular TeamCity If you have any questions please feel free asking it! )īut using plugins will allow you to run your code as a part of Agent JVM. It is possible to write plugin for the agent. TC server thus all changes properties will be published. The easyest way to solve you proble is to update ]]>/conf/buildAgent.propertiesįile from the other process/build/plugin. I'm not sure if the approach to only remove (very) old build results will work for us - a bunch of nightly builds can easily produce so much data that this could cause a build to fail as well - but it would be start anyway. Even if it's not used for not cleaning up, that information could also be used to indicate whether a build-agent is capable of running a build or not - which at least would reduce those ugly "Build failed. A sophisticated approach could be to keep some statistics about the amount of data a build usually generates and use that as a hint. only clean up if a build is certainly failing due to insuffient space (which can be caused by the output from previous builds).Ĭleaning up until "enough space is available" is difficult though - nobody knows how much data a build produces - at least initially. automatically cleanup unused work-folders. Of course I meant not to unconditionally clean up everything, but only in case not enough space and no other build agent is available: ". Unfortunately, I don't see anything in the plugin API that might allow me to tack this on. so I'm also willing to do this as a plugin. 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. I think a build agent property that specifies the current available disk-space would be very useful. 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 don't see anything in the agent properties that lists any real-time resource information about the box the agent is running in. so's to link against, starts to consume quite a bit of space. Pulling down a complete build workspace for each of these build runs, which for some projects also includes third-party. 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). 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |