tag:blogger.com,1999:blog-7290642316743338665.post4810874586996425361..comments2023-09-20T05:23:44.886-05:00Comments on behind the times: TeamCity Rocks!Hamlet D'Arcyhttp://www.blogger.com/profile/04008870357169725586noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7290642316743338665.post-58816514167239178982010-01-30T19:07:43.207-06:002010-01-30T19:07:43.207-06:00thank you great post
murat
muratolojithank you great post<br />murat<br /><br /><a href="http://www.muratoloji.com" rel="nofollow">muratoloji</a>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-65409544790200991472009-10-07T00:58:05.685-05:002009-10-07T00:58:05.685-05:00This feature of TeamCity relies heavily on IDE, an...This feature of TeamCity relies heavily on IDE, and it is only available for Visual Studio, IntelliJ and Eclipse for now. For developers using other IDEs (or even do not have an IDE), QuickBuild 2.0 might be a good choice to do continuous integration builds before commit. It includes a free community edition which allows to use up to 16 projects without any other limitations. For details, please <a href="http://www.pmease.com/features" rel="nofollow">checkout here</a>Robinhttps://www.blogger.com/profile/02739993585435877733noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-57044111688861496592008-09-20T19:32:00.000-05:002008-09-20T19:32:00.000-05:00sinemakurtlar vadisi pusu<A HREF="http://www.sinema24.net" REL="nofollow" TITLE="sinema">sinema</A><BR/><BR/><A HREF="http://www.kurtlarvadisi-pusu.in" REL="nofollow" TITLE="kurtlar vadisi pusu">kurtlar vadisi pusu</A>sadecedizihttps://www.blogger.com/profile/07038387367931336812noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-46411418142394126032008-03-24T03:31:00.000-05:002008-03-24T03:31:00.000-05:00More on TeamCity personal builds and when they are...More on TeamCity personal builds and when they are useful: http://teamcitydev.blogspot.com/2008/03/personal-builds-practical-experience.htmlpavelhttps://www.blogger.com/profile/11735149229329345300noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-60201709916932037532008-03-20T19:17:00.000-05:002008-03-20T19:17:00.000-05:00Hamlet,You might check out our Parabuild. It handl...Hamlet,<BR/><BR/>You might check out our <A HREF="http://www.viewtier.com" REL="nofollow">Parabuild</A>. It handles cases when changes that break the build do get submitted to the version control system, such as integration merges that you described. <BR/><BR/>We call this killer feature "unbreakable scheduled builds". With Parabuild your nightly and daily builds will be clean even if the head of the code base is broken. <BR/><BR/><BR/>Regards,<BR/><BR/>Slava ImeshevSlava Imeshevhttps://www.blogger.com/profile/01239648583875379220noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-23965925087962769352008-03-20T13:47:00.000-05:002008-03-20T13:47:00.000-05:00Yes, separate build agents are used. Which is nice...Yes, separate build agents are used. Which is nice, because any one pre-commit build will only have one person's change list in it, and a distributed build will generally be faster b/c you'll never be bottlenecked waiting for the previous used. <BR/><BR/>There is still the possibility of a post-commit build failure, though. If two people pre-commit simultaneously and there is a version control conflict/merge issue, then I would expect that the first person whose build completes would get checked in, and the 2nd person whose build completed would have their build fail on the final "check in to VC" step. But if the conflict results in a failing unit test then both users will have their code checked in which causes a post-commit build to fail. <BR/><BR/>So you might still get some build failures. It is possible, and I should never use words like "never" and "always". <BR/><BR/>I don't mean to sound like the JetBrains rep, but I've been really impressed with this product.Hamlet D'Arcyhttps://www.blogger.com/profile/04008870357169725586noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-87458328488976883922008-03-20T10:51:00.000-05:002008-03-20T10:51:00.000-05:00When multiple developers commit to the same projec...When multiple developers commit to the same project, will TC use different build agents for the same code base to verify the changes? I.e. dev 1 commits at 10am and a build starts, at 10:05 dev 2 commits. Will the second commit start on a different agent if one is available?Hellohttps://www.blogger.com/profile/01511075468665543874noreply@blogger.com