mercurial clone and first pull failing

I'm having trouble with getting the repository to the server running Teamcity.

It starts collecting changes and every time after a while it stops giving these errors.

Unable to collect changes
java.util.concurrent.ExecutionException: jetbrains.buildServer.vcs.VcsException:
Problem collecting changes for ' ::  ' : '"C:\Program Files\Mercurial\hg.exe" clone --pull -U https://*******:******** risingrock' command failed.
stderr: transaction abort!
rollback completed
abort: connection ended unexpectedly
stdout: requesting all changes adding changesets adding manifests adding file changes ....

It seems that the connection seems to end unexpectedly. But it happens every time.

I don't know if it is because of my ISP or bitbucket or mercurial. It also happens when i check out manually.

There is no problem when i pull to an existing repository. But Teamcity seems to always want to clone a new repository.

Is there an easy way to make Teamcity use an existing repository instead of cloning it completely?

1 comment
Comment actions Permalink


Such hacks can cause very weird issues later.
I would suggest to figure out the root cause of the problem.



Please sign in to leave a comment.