Should "Create Project From a repository URL" take 3 minutes or more?
I'm trying to figure out why it takes ages to create a project from repository URL from its initial step. Currently the amount of time required to create a project from a repository url, is obstructing our move from a different buildserver.
Each new project takes 3 minutes ++ to successfully add to Teamcity from our Bitbucket repository.
The only reference in the log (teamcity-vcs.log) for the new project is
[2017-09-26 10:55:48,675] WARN [-nio-80-exec-39] - jetbrains.buildServer.VCS - 'hg --config ui.interactive=False identify http://******:******@helseregister.no/stash/scm/dot/jiragatsync.git' command failed.
Is there something I can use to figure out what's slowing down the pull?
FYI A normal pull takes seconds on a workstation.
Please sign in to leave a comment.
Hi Harald,
initially it's common that it takes a bit longer than a pull, as new data has to be created and stored. Depending on the size of the repository, it might be normal that it takes longer, but 3 minutes still sounds like way too much, unless the repository is huge. Also, do you mean just for adding the repository, or does this timing include detecting the build steps?
If it's just for adding the VCS, could you share which version you are using and send us the full teamcity-vcs.log and teamcity-server.log (please, ensure that the time frame where you tried it is within the log) using the "Submit a request" button on top of the page.
This is the initial pull, before setting up the build steps.
On average a pull takes 2.5 minutes, I used a stopwatch to observe the time consumption. The repository is not big at all, it's a minor project which is below 1 MB and does not contain a lot of small files.
I'm using TeamCity Enterprise 2017.1.4 (build 47070)
I'll get a log entry later.
However I've observed there's a thread dump directory which contains a log indicating that the pull thread is waiting for something.
Thanks for the info. If you could attach the thread dump/s to the logs you send us, that might be helpful.
I was tinkering with the proxy settings on the Teamcity server, using the _JAVA_OPTIONS environmental variabel yesterday. Seemingly it must have done something since the pull from git is completed by the time I've pushed the "Proceed" button. The pull didn't work that fast yesterday, perhaps something has been flushed in the network since yesterday.
The server is within an enterprise environment with a network that runs through a proxy with whitelisting, which can make it hard to debug when something does not work.
BTW I wasn't aware that Teamcity has a version checker before I saw a reference to it in one of the logs and I reckon it is stopped by the proxy.
I'll report back on Friday with or without a log, if the current trend continues I won't need the log :)