Are You Doing Continuous Integration with Flex?

At our company we've been working with Flex and CI for the last few months now. We use fluint and I got a little frustrated at the lack of CI support, so I built it into the new 1.1.0 release. We also integrated xvfb-run support so that fluint can run its tests in the AIR Runner headlessly on any Linux platform running X windows. If you're using fluint/flexunit/asunit/etc you're gonna have to face the need for a windowing environment eventually, so that's probably the biggest hurdle for the CI process and Flex.

As far as build goes Ant works well and keeps things simple, but the flex-mojos plugin for Maven is pretty nice and we use it at the office. If you want dependency management and don't want to use Maven however, Apache Ivy is just as good, just requires a bit more config. I did a preso at FlexCamp Miami about Flex and CI using Hudson, Ant, and fluint. I hope to have it online with my code soon, if it can help any.

Good luck with the article, if you have any questions, just let me know.

We're using Hudson (with Xvnc plugin), flex-mojos, FlexUnit, and Flexcover on Debian servers. Like Marc, it took a bit to get through the issues, but now that it's working, it does pretty well, though we'd like to get our Flexcover automated (right now we run it manually). We've just started looking into FlexMonkey as well.

@Brian
That's good to hear about fluint. We'd like to start using it in the next month or two, and it would be great if it works with the rest of our stack.

I've been using Maven/Flex-Mojos, Artifactory, & Hudson to do CI for the past few months. It's worked great for us, and helped resolve a bunch of deployment issues. The leaderboard game is sweet too.

Recently, I set up an Ubuntu Server 8.10 machine running Tomcat and setting up the new builds couldn't have been simpler. Lately, I've been writing custom assemblies which zip builds for download by clients... pretty neat.

Still in the works - *should* be in the "issue after next" of Flex Authority.