On 5/8/12 10 :41PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> Personally I don't think anyone should spend much time on this until >>we've >> settled on how we're going to end up building this for the first >>release. > >Personally having the CI do a nightly build is still useful even if it's >doing a "standard" build rather than a release build. It would (for >instance) of picked up the issue with yesterdays build changes. > >It should take minimal work to set up as a first pass the script is >basically check out, set env vars and run ant (baring any issues with the >required downloads). Getting asdocs, mustella tests etc etc to run as >part of the CI may take some extra work but I wasn't thinking of doing >that as a first pass. Agreed. We had quite an elaborate CI setup for Flex. If needed I can go dig up those scripts (most are Python I believe) at some point just to make sure we don't end up missing some step. The first thing I'd like to see done is to generate a build number which is used in build.xml and defaults to 0 for dev builds. I'm pretty sure our build number used to be the svn commit # of the checkin that generated the change (but we were in the 20,000s not the 1.4 millions like Apache is). Carol >
