TeamCity build is slow compared to Command line build
Team-city build takes longer than command line build using the same machine. We are using MSbuild and Run Octo pack in the build step and there is a time trial difference of at least 40 mins between the two methods. I verified the logs and I do not see and hanging build steps. I would really like to debug this as much as I can to optimize the performance of Team-city builds. Is there an lead direction on where to debug further.
Please sign in to leave a comment.
Hi Nikitha,
First it would be useful to consider the global time and not just the difference. For a build that takes 5 seconds, 40 minutes is insanely long, while for a build that takes several hours 40 minutes might not be all that much.
For debugging it, I recommend checking the timestamps on the build log page. While there isn't necessarily a hang or anything, it might show you whether some bits are taking much longer, or it's just a longer delay on everything. If this is the case, there might be some resources being hogged on the TeamCity agent machine. We have some troubleshooting steps here for when a build behaves differently on TeamCity and locally: https://confluence.jetbrains.com/display/TCD18/Common+Problems#CommonProblems-BuildworkslocallybutfailsormisbehavesinTeamCity