TeamCity: builds have became run more an hour
Hello, we next problem: we have android builds in Teamcity(2017.1.4) for build .apk files. Firstly common time builds was about 30 mins, later builds have became run 40/50/60 mins and more. What is reason it behavior: Teamcity or our builds? How can we optimaze this process?
Please sign in to leave a comment.
The workflow to detect this changes is to access the build log, where all the steps on a build are logged, then check the timestamps for what is taking the longest. That should give you a hint on what is taking the longest, and whether it is teamcity-related or build process related.
If this behaviour only reproduces on TeamCity, if your local development builds are as fast as they used to be, please check the two following articles for instructions on troubleshooting:
Slowness: https://confluence.jetbrains.com/display/TCD18/Reporting+Issues#ReportingIssues-Slowness,HangingsandLowPerformance
If the time for the builds has changed differently in teamcity than in the local installation: https://confluence.jetbrains.com/display/TCD18/Common+Problems#CommonProblems-BuildworkslocallybutfailsormisbehavesinTeamCity
Hello, we have noticed that a main problem, is build node modules. It takes more hour. What can you recommend?
I can recommend checking the history of that build through their build logs and see which steps are taking much longer than before. It's hard to know what is going on without that information. If you can trace the issue to teamcity itself please don't hesitate to provide 2 build logs, one of the time when it took much shorter than now and a recent one so that we can check the differences.