Collecting changes build step times out randomly
Hi,
We have TeamCity Enterprise 2024.07.1 (build 160635) and recently the collecting changes step in the build times out randomly with this error
Failed to collect changes, error: Timeout exception: jetbrains.buildServer.vcs.VcsException:
Would like to know how to get more details about this timeout.
Will switching the active logging preset from <default> to “debug-vcs” help?
Also, at the moment, it times out after 60 seconds. How do we increase the timeout in this case?
Any help in this regard would be really appreciated.
Thanks,
Paul
Please sign in to leave a comment.
Hi,
If it is Git VCS, it is possible to configure the following internal properties (https://www.jetbrains.com/help/teamcity/server-startup-properties.html#TeamCity+Internal+Properties):
teamcity.git.idle.timeout.seconds
For more detailed information please refer to https://www.jetbrains.com/help/teamcity/git.html#internalProperties
If it doesn't help, please enable the debug-vcs (https://www.jetbrains.com/help/teamcity/teamcity-server-logs.html) logging preset on the Administration > Diagnostics > Troubleshooting page. After that, reproduce the issue and provide the following information:
• the entire build log downloaded from the UI
• a screenshot of the VCS Root configuration
• teamcity-server.log
• teamcity-vcs.log
Please ensure all logs cover the timeframe of the build. Once completed, revert the logging preset back to <Default>. Files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.
Best Regards,
Tom
Hi Tom,
Thanks for your response. Yes, we have the issue with Git VCS. Hence, will try setting the internal property and see how long it takes.
If it takes considerably long time, will generate the logs as you suggested and share it.
Regards,
Paul
Hi Tom,
Sorry, but I see the default value for teamcity.git.idle.timeout.seconds is 1800 and we are not overriding the value in our instance.
But if you see the log below, it times out after 60 seconds. Any idea why?
11:33:20 Collecting changes in 2 VCS roots
11:34:21 Failed to collect changes, error: Timeout exception: jetbrains.buildServer.vcs.VcsException: "C:\Program Files\Git\cmd\git.exe" -c core.askpass=C:\TeamCity\temp\pass18072120607890830040.bat -c credential.helper= -c credential.helper=C:/TeamCity/temp/cred1678724391343610482.bat ls-remote origin command failed.
exit code: -1
Thanks,
Paul
From the log information, it appears there was a timeout after 60 seconds. Could you please share the relevant details I mentioned in my previous email for forther investigation?
Additionally, would you mind adjusting the value of teamcity.git.idle.timeout.seconds to see if it makes a difference?
Best Regards,
Tom
Hi Tom,
Thanks for the update. I tried adding the line “teamcity.git.idle.timeout.seconds=1800” in the internal properties tab under Diagnostics on TeamCity but couldn't restart the server as I would need to find a maintenance window to do that. Without server restart, it didn't have an impact as we still have some timeouts. I will find a window to restart the server and get back to you.
Regards,
Paul
Thanks for your response.
If the internal property does help, please share the following items with us for further investigation.
• the entire build log downloaded from the UI
• a screenshot of the VCS Root configuration
• teamcity-server.log
• teamcity-vcs.log
Files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.
Best Regards,
Tom
Hi Tom,
Sorry for the delay in getting back to you.
After adding the internal property and doing a server restart, we haven't faced timeouts in the last few days.
If we face this issue again, will share the details requested.
Thanks for your help.
Regards,
Paul
Glad to know that you don't face the issue again.
Please do not hesitate to reach out to me if you have any further inquiries regarding this matter.
For now, I will close this ticket.
Best Regards,
Tom
Hi Tom,
Sorry, I think I spoke too soon. Yesterday, unfortunately, we again had a timeout in one of the builds where it timed out after 1 minute. Hence, seems like it didn't consider the timeout value set in the internal properties.
If you have other suggestions to increase the timeout, please let me know.
Meanwhile, I will check the possibility of sharing the details you had requested.
Thanks,
Paul
Files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.
Best Regards,
Tom
Hi Tom,
Sorry for not getting back to you earlier. We recently upgraded the version to TeamCity Enterprise 2024.12 (build 174331).
Will monitor the builds and share the details if we come across this issue in this new version.
Thanks,
Paul
Please do not hesitate to reach out to me if you have any further inquiries regarding this matter.
Best Regards,
Tom