My team wants to set up a continuous integration server for a flex 4 project that we are developing. I have been evaluating various options and have some questions.
Really torn between Cruise Control and Hudson/Jenkins. Continuous integration servers for Flex shows at least two successful installations of Hudson for Flex.
Which source control should we use? I am personally inclined towards GIT, but looks like SVN has a lot more in-built support in both CC and Hudson.
In the worst case scenario, we might be forced to use VSS. What is the support for VSS like?
Regards, Ravi.
First, NEVER USE VSS. Biggest POS out there. Cruise Control/Hudson/Bamboo/Teamcity/etc are just build servers, but they need something to build with like Ant or Maven. After the build is done, they normally deploy whatever was created to your place of choosing. Any one of them will work just fine unless you have some very specific requirements.
As for version control, all of them can be used with the build server so it comes down to preference. In a team environment, I prefer Git; however, it is a bit more 'complex' to use than subversion, so training might be involved. But trust me, a lot less headaches merging with Git than subversion.
The most important part of the whole equation is your Ant or Maven build file. I personally recommend using Maven over Ant since the dependency management is wonderful for larger projects. You'll also want to take a look at the FlexMojos project to compile/test your Flex application.