Comments on: Hudson and Symfony continuous integration http://www.whiteoctober.co.uk/blog/2010/02/05/hudson-and-symfony-continuous-integration/ great stuff about the web Sun, 27 Nov 2011 13:43:26 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Kraig Godden http://www.whiteoctober.co.uk/blog/2010/02/05/hudson-and-symfony-continuous-integration/comment-page-1/#comment-2507 Kraig Godden Thu, 30 Sep 2010 11:56:49 +0000 http://www.whiteoctober.co.uk/blog/?p=460#comment-2507 We are using Hudson to manage a bunch of custom builds and like the quickness afforted by Hudson in configuring a build. One of the issues we are trying to resolve is when there are two different branches involved in producing a build. For example, many of our products use a common library, and occasionally a new branch of that common library is needed, along with the branch of a module (different modules). It appears that Hudson's CVS setup only allows us to identify one branch, when what we need is a second CVS setup to identify an additonal branch. Does anyone know how to handle such a situation? We are using Hudson to manage a bunch of custom builds and like the quickness afforted by Hudson in configuring a build. One of the issues we are trying to resolve is when there are two different branches involved in producing a build. For example, many of our products use a common library, and occasionally a new branch of that common library is needed, along with the branch of a module (different modules). It appears that Hudson’s CVS setup only allows us to identify one branch, when what we need is a second CVS setup to identify an additonal branch.

Does anyone know how to handle such a situation?

]]> By: Rich http://www.whiteoctober.co.uk/blog/2010/02/05/hudson-and-symfony-continuous-integration/comment-page-1/#comment-2385 Rich Wed, 10 Mar 2010 11:49:35 +0000 http://www.whiteoctober.co.uk/blog/?p=460#comment-2385 We use Lime, as obviously it comes with Symfony and it's got a pretty low entry barrier to getting started and using it for tests. In particular, the functional tests are the aspect that is probably the most useful for us. It's definitely extensive enough for projects we've done - at the end of the day, the methods available in Lime will cover most of what you'll need to do in your unit and subsequent functional tests so it's been great for us. We use Lime, as obviously it comes with Symfony and it’s got a pretty low entry barrier to getting started and using it for tests. In particular, the functional tests are the aspect that is probably the most useful for us. It’s definitely extensive enough for projects we’ve done – at the end of the day, the methods available in Lime will cover most of what you’ll need to do in your unit and subsequent functional tests so it’s been great for us.

]]> By: xzyfer http://www.whiteoctober.co.uk/blog/2010/02/05/hudson-and-symfony-continuous-integration/comment-page-1/#comment-2384 xzyfer Wed, 10 Mar 2010 11:40:08 +0000 http://www.whiteoctober.co.uk/blog/?p=460#comment-2384 i am looking to implement a similar solution for my company's new symfony project. question for you: are you using phpunit or just lime? is you are simply using lime, do you find it extensive enough to cover you testing needs? i am looking to implement a similar solution for my company’s new symfony project.

question for you:
are you using phpunit or just lime?
is you are simply using lime, do you find it extensive enough to cover you testing needs?

]]>