<p>I have a Team Foundation Server 2008 Installation and a separate machine with the Team Build service.</p>

<p>I can create team builds and trigger them manually in Visual Studio or via the command line (where they complete successfully). However check ins to the source tree do not cause a build to trigger despite the option to build every check in being ticked on the build definition. <strong>Update: To be clear I had a fully working build definition with the CI option enabled.</strong></p>

<p>The source tree is configured is a pretty straight forward manner with code either under a <em>Main</em> folder or under a <em>Branch\branchName</em> folder. Each branch of code (including main) has a standard Team Build definition relating to the solution file contained within. The only thing that is slightly changed from default settings is that the build server working folder; i.e. for main this is <em>Server:"$\main" Local:"c:\build\main"</em> due to path length. </p>

<p>The only thing I've been able to guess at (possible red herring) is that there might be some oddity with the developer workspaces. Currently each developer maps Server:"$\" to local:"c:\tfs\" so that there is only one workspace for all branches. This is mainly to avoid re-mapping problems that some of the developers had previously gotten themselves into. But I can't see how this would affect CI.</p>

<p><strong>UPDATE: Ifound the answer indirectly; please read below</strong></p>

[{'answer_id': 47600, 'author': 'Justin Dearing', 'author_id': 3110, 'author_profile': 'https://Stackoverflow.com/users/3110', 'pm_score': 0, 'selected': False, 'text': '<p>Select your team project from team explorer, then right click on the Builds folder.  Select a new build definition and then select the trigger tab.  Move the radio button to "Build each check-in (more builds)"</p>\n\n<p>More info can be found here</p>\n\n<p><a href="http://msdn.microsoft.com/en-us/library/ms181716.aspx" rel="nofollow noreferrer">MSDN How to: Create a Build Definition</a></p>\n'}, {'answer_id': 50860, 'author': 'Mr. Kraus', 'author_id': 5132, 'author_profile': 'https://Stackoverflow.com/users/5132', 'pm_score': 0, 'selected': False, 'text': '<p>Are there any errors in the log on the TFS application server?  Anything that indicates that it tried to fire but failed?</p>\n'}, {'answer_id': 56511, 'author': 'Lex', 'author_id': 4109, 'author_profile': 'https://Stackoverflow.com/users/4109', 'pm_score': 2, 'selected': False, 'text': "<p>Ok I have found the answer myself after several dead ends. In the end I fixed this unintentionally while fixing another issue. Basically we had just turned on the automatic execution of unit tests for our builds. The test would run sucessfully but then immediately the build would bomb out with a message saying it was unable to report to the build drop folder. </p>\n\n<p>What was happening was that while the Build service runs under one account and has a set of rights; some of the functionality is actually driven through the TFSService account. fter wading a heap of permissions I had my tests being reported. Then I noticed that builds had started to trigger on check-ins; I can't tell you exactly which permission fixed this but hopefully this answer will at least set people down the right path.</p>\n\n<p>One other note a few of the builds started failing due to conflicting workspace mappings - this was a separate issue that I resolved by deleting some obsolete workspaces using the Attrice Sidekicks for Team Foundation tool.</p>\n\n<p>Hope this helps somebody else.</p>\n"}]
['https://Stackoverflow.com/questions/43815', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/4109/']