To start we are a Java back end shop so our tools are slanted toward the java tools.
For source control we use SVN (Subversion). For Continuous Integration we use Hudson, but there are others like Cruise Control. This basically will monitor source control and when there is a change it will checkout the project from source control, build it, run all your unit tests and keep a history of the builds. If it fails you can have it email to the team. Very configurable. Basically is continuously testing your application. Build scripts we use Maven as our main build tool, but since Flex does not have good Maven integration we use Ant for building our Flex code. Maven will still control all of the building though and will just call out to Ant when it is time to build our Flex application. I can say that after using Maven, I wish we would have just used Ant for the entire build scripts, but too late for us now. This was a very, very high level response if you want more details I'd be happy to meet with you at the next AFFUG meeting and discuss in more detail. Dale From: [email protected] [mailto:[email protected]] On Behalf Of Frank Griffin Sent: Thursday, March 12, 2009 5:03 PM To: [email protected] Subject: RE: [AFFUG Discuss] Bin-release folders I agree, Dale. In my case, to goes to the Development environment, to the Testing-QA environment and then to production all of which are completely separate environments. "Build Scripts", I don't see that in Flex3 Builder. What are you using for source control? Also, would you elaborate on "continuous integration box"? Thanks, Frank _____ From: [email protected] [mailto:[email protected]] On Behalf Of Dale Bronk Sent: Thursday, March 12, 2009 4:45 PM To: [email protected] Subject: RE: [AFFUG Discuss] Bin-release folders I would actually recommend not using the "Export Release" at all even when sending a release beyond development. Instead, use build scripts that first checkout from your source from source control and build. Preferably this should not be done from a developers box at all and instead from a dedicated build and continuous integration box. My believe it is not a wise idea to go from a developer box to a deployable build. Dale From: [email protected] [mailto:[email protected]] On Behalf Of Douglas Knudsen Sent: Thursday, March 12, 2009 4:36 PM To: [email protected] Subject: Re: [AFFUG Discuss] Bin-release folders Frank, I'm not sure why you end up with multiple bin-release directories. But I will point out, if testing during development, or any general 'before QA' testing, just hit the debug button or run button. The former will kick the debugger links off of course. Perform a 'Export Release' when you are truly ready to release your code to a larger audience, whomever that may be. DK Douglas Knudsen http://www.cubicleman.com this is my signature, like it? On Thu, Mar 12, 2009 at 3:31 PM, Frank Griffin <[email protected]> wrote: In order to test each little change I make to my application I have to do an "Export Release Build" so now I have all these bin-releases in my project. Each time I do a new release it not only adds another one but it updates the others as well. How can I get rid of all these extra bin-releases? I see that I can delete the link from the project but I don't know what else I need to do to keep my project clean and lean. :-) Thanks, Frank ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by FusionLink <http://www.fusionlink.com> ------------------------------------------------------------- ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by FusionLink <http://www.fusionlink.com> ------------------------------------------------------------- ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by FusionLink <http://www.fusionlink.com> ------------------------------------------------------------- ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
