Menu
I have a teamcity server configured for CI. Our svn connection occasionally drops, once this happens a project will no longer check for changes, but we are not warned about this without logging onto the servers' web page.
Is there a way to be notified when there is a VCS problem in Team City?
758
VCS triggers automatically start a new build each time TeamCity detects new changes in the configured VCS roots and displays the change in the pending changes. Multiple VCS triggers can be added to a build configuration.
In the web UI, go to Administration | Diagnostics page. On the Troubleshooting tab, choose an active logging preset. To view logs, go to the Server Logs tab. If it is not possible to enable debug logging mode from the TeamCity web UI, refer to this section to learn how to adjust logging options manually.
TeamCity core uses log4j 1.2 which is not vulnerable. To confirm its safety we have run additional tests through the known attack vectors which did not replicate the issue.
To run a custom build with specific changes, open the build results page, go to the Changes tab, expand the required change, click the Run build with this change, and proceed with the options in the Run Custom Build dialog. Use HTTP request or REST API request to TeamCity to trigger a build.
Do you use mail notification on you builds? If so, you can set it to be notified of "Build fails to start". There may be different reasons to fail, but for us, it is always losing connectivity to VCS server.
Subscribing to Notifications
Failed to Start Builds
52
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
