Why is TeamCity generating different hashes for checkout directory?
Does anyone know why TeamCity might be choosing to check out to different folders in the \work directory, even when they're running from the same VCS root with exactly the same configuration settings?
This is a typical contents of the "directory.map" folder:
bt3=Developer Fusion::Build entire solution -> bd38381feb233fe8 |?| Jul 1, 2011 3:27:43 PM BST |:| default
bt12=Developer Fusion::Deploy to Production -> eaec9519d8913c73 |?| Jul 1, 2011 3:22:13 PM BST |:| default
bt10=Developer Fusion::Deploy to Staging -> 304467e0a1317de6 |?| Jul 1, 2011 3:29:18 PM BST |:| default
each of those build configuration has the following:
<vcs-settings checkout-mode="ON_SERVER" labeling-type="SUCCESSFUL_ONLY" labeling-pattern="build-%system.build.number%">
<vcs-entry-ref root-id="2" set-label="true" />
</vcs-settings>
What else could be causing the hash to change?
Thanks
James
Please sign in to leave a comment.
Do you mean that all of these build configurations have the same VCS roots and checkout rules?
VCS settings hash consists of checkour directory, VCS root settings, checkout rules and type of checkout. If all of this is the same in your case, I would appreciate if you could share your settings with us, to reproduce this problem locally.
Hi Pavel - yes, that's right. Is there an email address I can reach you on to send you the build config file?
Thanks
James
teamcity-feedback[at]jetbrains.com