Build time by Teamcity UI is 4x slower than comum build;

Unity Engine
1

Hello, I’m facing a problem with Teamcity build time, and I’d like to know if someone else already faced this, or can guess a possible problem.

I’m running a build Android script such this "C:\Program Files\Unity\Hub\Editor\2019.2.10f1\Editor\Unity.exe" -batchmode -projectPath [etc], in a build step on TeamCity, and this step is taking 4x more time than if I open the CMD in server system, copy the script, and run it.

The tests I made, both have ran with the same configuration, and without replace the files, i.e., I’m not cleaning build path before build it.

1 Like
2

Does your Etc include specifying the build target? Perhaps NOT specifying the build target is causing Unity to reimport all for PC on launch, THEN reimport for your target. Just try supplying the intended target you know it is already set to build and see.

1 Like
3

Thank you, Kurt, for the answer.

Yes, it has the build target, I didn’t put all the script because it is not really important.
The deal is most related to: why the same script running in the same machine has such different time, being that the only general difference is that one is being running by the UI of Teamcity, and the other is not.

I think this is most related to TeamCity knowledge.