Moreover some of our builds produce a large number of small files on disk. The files are then deleted by build itself or by agent but this increases fragmentation of the file system. Not surprisingly these builds started to run slower, and we decided that we need some kind of agents maintenance policy. Ideally we need to defragment agent disk and probably reboot agent once per week. Well, since we already have agents installed on these PCs why not do maintenance tasks with еру help of the agents themselves?
The solution
Note: we did not experience performance problems with Unix/Linux based agents so all the scripts below are for Windows only.
First of all we created a project in TeamCity and set necessary access rights. Authorization is important since maintenance tasks are potentially harmful and only experienced users should be able to configure and run them.
Then we created three build configurations:
1) Clean & Defragment
2) Reboot
3) Run all
"Clean & Defragment" build configuration removes temporary files from the user home directory and starts disk defragmentation. Currently it is Ant based, and here is the script we use:
<project name="AgentsMaintenance" default="defragment" basedir=".">
<target name="defragment">
<echo message="##teamcity[progressMessage 'Defragmenting ...']"/>
<exec executable="defrag">
<arg value="C:"/>
<arg value="-v"/>
</exec>
</target>
<property environment="env"/>
<property name="userTemp" location="%env.USERPROFILE%/Local Settings/Temp"/>
<target name="clean">
<echo message="##teamcity[progressMessage 'Cleaning ${userTemp} directory...']"/>
<delete quiet="yes" failonerror="false" includeemptydirs="true">
<fileset dir="${userTemp}" includes="**/*"/>
</delete>
<mkdir dir="${userTemp}"/>
</target>
</project>"Reboot" build configuration reboots an agent. It uses command line runner and simply invokes the following command:
shutdown -r -f -t 20 -c "Reboot build agent"
And finally the main step is build configuration "Run all". Here is the Ant script:
<project name="AgentsMaintenance" default="runAll" basedir=".">
<target name="runAll">
<property name="user" value="username"/>
<property name="pwd" value="password"/>
<get src="http://teamcity.server.com/httpAuth/action.html?add2Queue=<clean&defrag conf id>&agentId=allEnabledCompatible"
dest="response.txt" verbose="yes" username="${user}" password="${pwd}"/>
<get src="http://teamcity.server.com/httpAuth/action.html?add2Queue=<reboot conf id>&agentId=allEnabledCompatible"
dest="response.txt" verbose="yes" username="${user}" password="${pwd}"/>
</target>
</project>Where <clean&defrag conf id> and <reboot conf id> are identifiers of the corresponding build configurations (buildTypeId from the TeamCity URLs).
"Run all" build configuration is triggered by TeamCity scheduling trigger at Saturday night. The build of this configuration adds "Clean&Defragment" and "Reboot" builds in the queue. It uses not yet released feature of TeamCity allowing to start a build on all compatible and enabled agents (note agentId=allEnabledCompatible in the URL). So if you do not want "Reboot" builds to run on some agent just make this agent incompatible with "Reboot" configuration! Pretty simple, isn't it?
So far the solution works nice. And if your builds started to run slower try to setup something like this, probably the reason is not in the builds itself. BTW the new feature to run build on all compatible agents will be available in the next EAP build.
