Personal build doesn't get .SLN files
I'm attempting to submit a personal (test) build that includes a changed .H file and a .SLN file.
In the log I see:
Item guid://ccae615b-e07a-46b5-b523-fafd3062efb1/$/src/SLN/Toolkit.sln was mapped as SLN/Toolkit.sln and was skipped due to configured checkout rules
How can I resolve this?
Please sign in to leave a comment.
I just tried with an add of a new .SLN, and it too is skipped. Any clues?
Another observation from the log:
[12:30:01] The build is removed from the queue to be prepared for the start
[12:30:01] Collecting changes in 1 VCS root
[12:30:01] VCS Root details
[12:30:01] Detecting changes in VCS root 'tfs: http://tfs:8080/tfs/Toolkit/ $/src' (used in 'xxx', 'yyy' and 110 other configurations)
[12:30:01] Will collect changes for 'tfs: http://tfs:8080/tfs/Toolkit/ $/src' starting from revision 159971
[12:30:01] Compute revision for 'tfs: http://tfs:8080/tfs/Toolkit/ $/src'
[12:30:01] Starting the build on the agent CDLL20CI32
[12:30:07] Clearing temporary directory: C:\C1\temp\buildTmp
[12:30:07] Publishing internal artifacts
[12:30:07] Using vcs information from agent file: 635529fe35b4bcd.xml
[12:30:07] Checkout directory: C:\C1\w\635529fe35b4bcd
[12:30:07] Updating sources: auto checkout (on agent) (13s)
[12:30:07] Will use agent side checkout
[12:30:07] VCS Root: tfs: http://tfs:8080/tfs/Toolkit/ $/src (13s)
[12:30:07] checkout rules: xxxxxxxxxxxxxxx; revision: 159967
[12:30:07] Using .net working mode
[12:30:07] Receiving workspace (1s)
[12:30:09] Using workspace TeamCity-A9-7dd5f67e6e824d558ac9350f75a1f589;xxx;xxx
[12:30:09] Updating sources to revision: 159967
The revision # at the start is correct: 159971
But the update is the PREVIOUS revision #: 159967. Why?
Hi Ike, sorry for the delay,
please send us the full build log via the submit a request button above. It would also be helpful if you specified how exactly you are starting the personal build (scripts, custom run, IDE plugin...)
Unfortunately I don't have the logs. We cleaned everything, and removed all the folders from the agent's working directory and now I cannot reproduce the issue :(.
Well, if it works now it might have been an issue with a very specific state. If it happens again please collect the info mentioned above and send it to us for review.
error - was skipped due to configured checkout rules
what should i do to resolve this ?
Hi,
as I mentioned to Ike on the last post, we don't know what produces this and need a set of logs to try to determine it. Please collect those I mentioned and forward them to us for review.