We have 2 build configurations for our .NET Silverlight application:
- Main - Continuous
- Main - Continuous Silverlight Tests
The first configuration is setup to fire on every checkin (with 60 second quiet period) and the second configuration fires off immediately on a successful completion of the first configuration. The task of the second configuration is to automate the run of our Silverlight UI Tests using the Microsoft Silverlight Testing Framework. This all works 100% until we get a failure in one of the tests of the 2nd configuration. It then seems like TeamCity goes into recursive loop trying to build the 2nd configuration due to the fact that the it somehow didn't get a response from the build Agents. This results in a new build being spawned every few seconds but no progress is actually being made as the build would startup, run for a few seconds and then close down. A new build will then start again and this process continues until I pause the actual build configuration.
I tried rebooting all the agents and the TeamCity web server, but as soon as these are up and running again and I "unpause" the build configuration, it again starts looping. Currently the only way for me to solve the issue is to Copy the 2nd configuration into a new configuration, delete the existing configuration and then get the new configuration enabled for all the build agents. This works only until I get the first failure whereafter the build starts looping again.
Find attached 2 screenshots that show the information I have to my disposal to highlight the issue. Can you please urgently assist.
Other useful information:
- Using MSBuild runner for .NET Framework 3.5
- TeamCity 4.5.4 (build 9071)
- Checkout mode: Automatically on server
- Checkout directory: Both the first and the second configuration share the same checkout directory
- Build Trigger: As mentioned, the 2nd configuration is set to depend upon the 1st configuration