Big checkout and artifacts folders

Hi!

I am having a few issues with my TC integration.

Perforce check out

I have a very large check-out folder (total size 1.46 GB). I set the "Checkout directory" and un-check "Clean all files before build". Most of the time it works, but sometimes TC starts checking out without any need. I want TC only run p4 sync on each of the roots and do nothing else. If something fails I would rather have an option to force cleaning once.

Artifact Dependencies

Similarly I have pretty big artifacts folder (234 MB). Main build triggers a test build, which requires the artifacts (build artifacts dependencies). This does not work very well either, because TC is "hanging" in "Resolving artifact dependencies..." for a long time. It would be great if build trigger allowed the option of running on the same agent which trigger this build.

3 comments

Perforce check out


TeamCity makes clean checkout in the following cases:
- this is the first build on the agent
- build configuration VCS settings or VCS roots were changed
- a patch failed on the agent
- if you are using personal builds you may experience such behavior if personal build was canceled on the agent (this is a bug and it is already fixed in TeamCity 4.0)
- please check that you do not have two build configurations using the same checkout directory but different VCS roots

Artifact Dependencies


How many files do you download? Artifact dependencies performance depends mainly on the number of files because each file requires separate request to a server.

--
Pavel Sher

0

Thanks for reply. I did get the feeling that my poking around with configuration had something to do with clean check outs. I hope you did get the logic right there, but still your perforce integration needs to be looked at. I think you have not tested it well with huge repositories, which is understandable.

0

Thanks for your suggestion. We really do not have so huge Perforce repositories (some of our projects stored in Perforce have size about 700Mb), however we constantly improve VCS support part of TeamCity. Some bugs causing undesirable clean checkout are already fixed in 4.0. Probably we should also take a look at performance of patch transferring from the server to agent, since the result of clean checkout is cached on server, full sync with Perforce should be done relatively rare, but transferring of a patch occurs every time.

--
Pavel Sher

0

Please sign in to leave a comment.