I'm trying to setup a gated check-in build (vNext) on a TFS2015.3 server. After I check-in a modification the build is triggered. The build runs smooth but the modified files are remaining locked by Project Collection Build Service (TEAM FOUNDATION).
From the build logs I can see that the "Check in gated changes" step is performed correctly.
If the team project source control has the multiple check-out option disable I'm not able to modify the locked files unless I unlock them or we queue the build again.
Any idea how to determine the gated check-in build to unlock the files at the end?
Update
After more tests I've found that the gated check-in build is releasing the files on a newly created collection; the locking issue is happening on a collection upgraded from TFS2012.
Update 2
Manually running again (after a gated check-in) the build cause the files to be unlocked:
Undo any pending changes under workspace.
tf undo Undoing edit:
D:\B\2\3\s\ConsoleApplication1\Program.cs
Update 0929
@danielstefanescu - looks like it was fixed yesterday. Should be in next update (2.107.1)
bryanmacfarlane commented
Related issue:tf undo at end of a shelveset/gated build #588
This phenomenon also occurs with some others. However, test in my environment, works pretty well with the collection created by TFS 2015 (don't have the collection upgraded from TFS 2012).
According to the link above, seems close Visual Studio and come back a bit later the files no longer show checked out. However, after checking in more changes and the next gated check-in succeeded but now the files still show checked out again by "Project Collection Build Service (TEAM FOUNDATION)". You can also give a try with your side.
This is very likely a BUG. And I have key one in Microsoft connect site. You can follow the action of it and also share the information if you have found some more useful trouble shootings.
Gated check-in build still locking files even after the build finished https://connect.microsoft.com/VisualStudio/feedback/details/3100862