Note that there are some explanatory texts on larger screens.

plurals
  1. POTFS2010 - Wrong changeset appearing at SourceGetVersion
    primarykey
    data
    text
    <p>I am currently setting up a Team Foundation Server 2010 and I found a very strange behavior when performing a build:</p> <p>The situation explained: We have 2 Branches </p> <ul> <li>Development</li> <li>Main</li> </ul> <p>All developers check in code into the Development branch only. Once per day, the build manager merges some changesets over to the Main branch. On the Development brach, a continuous build at each check in is running. On the Main branch, once per day (in the night) a build is triggered. </p> <p>Now suppose that the changesets 1-100 are being merged into the Main brach at 5pm, giving changeset 101 as the merge operation. Some developers check in changesets 102-106 after 5 o'clock into the Development branch. Now at 11pm the daily build is automatically triggered and runs on the Main branch. The last changeset of the Main branch is changeset 101. However, the Build details shows changeset 106:</p> <p><img src="https://i.stack.imgur.com/Nh0rc.png" alt="enter image description here"></p> <p>I could imagine that this behavior is intended, because if you check out changeset 106 on the Main branch, you will in fact get the content of changeset 101. But it would be much more readable if this Build summary showed the correct number.</p> <p>Question 1: Is there a way of manipulating the ouput of the SourceGetVersion information? Maybe through the Build Process Template?</p> <p>The second scenario, where the TFS behaves strange is even worse: When queuing a new build, there is the option of entering the "Get Version" Parameter, as shown in the following picture:</p> <p><img src="https://i.stack.imgur.com/dzIQ6.png" alt="enter image description here"></p> <p>If I now click on "queue", the build is triggered and AGAIN the build detail outputs the changeset 106 although I specifically set it to get changeset 76.</p> <p>Question 2: Is this a bug? Is there a hotfix or something to fix this? Or is there any option flag that has to be set?</p> <p>I hope someone knows more about this. I don't really believe that this is a bug, because it is such a vital functionality that other people must have encountered it before. </p> <p>Thanks for any help!! Christian</p> <p><strong>EDIT 1</strong></p> <p>The folder structure of the Team Project is:</p> <p>$ProjectName</p> <ul> <li>BuildProcessTemplates </li> <li>Documentation </li> <li>SourceCode <ul> <li>Development &lt;-- this is a branch <ul> <li>3rdParty</li> <li>Source</li> </ul></li> <li>Main &lt;-- this is a branch <ul> <li>3rdParty</li> <li>Source</li> </ul></li> </ul></li> </ul> <p>The build only pulls the Main branch and everything below it.</p> <p><strong>EDIT 2</strong></p> <p>Here is a picture of the Workspace tab in the build definition: <img src="https://i.stack.imgur.com/2zJXI.png" alt="enter image description here"></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload