So, I've got this shiny new mac provided by my new employers, and so I figured I'd put it to use as a CruiseControl build manager. I found the process reasonably simple but, just like the process of setting up Subversion and SCPlugin, there are a couple of extra steps I figured I'd share...
I just had to sort out getting subversion up and running on a mac. It's not quite as simple a process as on a PC; there are a couple of extra steps I thought I'd share...
Continue reading "Subversion and Finder integration for the Mac" »
so today, firefox decided to die a death on me. I choked it doing some Flex debugging and as a result I lost the functionality in my search bar. This got me thinking about what would really be useful for me is a way to search the places I usually go for flex info - the livedocs and the flexcoders mailing list. What I've ended up with is a quick way to search both these resources at the same time...
As I mentioned a few posts ago, I am looking into how asunit and flexunit can fit into our continuous integration set up. The move into AS3 has given me an opportunity to reassess how the 2 frameworks fit my/our needs. The prior post set out the criteria I was testing against - here is what I found...
When I started looking into how we could use flexunit in our CI build, I was struck by how the UI is closely linked to the actual running of the test suite. I really wanted to be able to use the supplied flexunit GUI out of the box - after all, it does everything the developer needs, and yet in order to have the results understood by our build process, we would need the results printed out differently.
To acheive this, my Flexunit test harness uses a factory method pattern to decide how torunthe test suite. Here's how...
If you read my earlier posts on Flex and continuous integration, you will remember that we had to do some work to get ASUnit to spit out its results in a manner that would be understood by Cruise Control. We built a log parser to parse results from the Flash players trace file into an XML file detailing the unit test results, and also a simple status file saying if the test suite succeeded or failed. Here's how I got FlexUnit to print out results that will be understood by our parser...
Continue reading "FlexUnit for Cruise Control - XML output" »
In this, the final entry on CI with Flex, I look at an extra change we made to the ASUnit sources, take a look at what CI has done for us, and finally let you in on what we are looking at next...
Continue reading "Continuous Integration with Flex - Part 6" »
This is the penultimate installment of the CI saga, and its the last step you will need to take to get your continuous integration suite up and running. The first thing you will need to do is install CruiseControl onto your build monitoring machine. The first thing I did was get it up and running on my machine, and then re-follow my steps on a server.
CruiseControl is an open source build monitoring tool. The good thing about it is that it can be easily configured using an XML file, has plugins to lots of other tools , and has a simple to understand web based interface. I just installed from the binaries, and followed these quickstart instructions. One thing I did have to do that wasnt covered in the instructions is set an environment variable, JAVA_HOME to the location of java on my machine (in my case: C:\Program Files\Java\jdk1.5.0_04). Once you have it up and running with the simple connectfour example, we are ready to get going with our flex project.
Continue reading "Continuous Integration with Flex - Part 5" »
Ok, so far so good. We had covered a lot of ground up to this point, but we were only part of the way there… The next step is to get our test results understood by ANT. Ikezi created a natty python script to parse the output of our flash logfile using some cunning regular expressions. Basically, it looks for a multiple line match of __TRACERUNNEROUTPUTBEGINS__(somestuff in here)__TRACERUNNEROUTPUTENDS__, then parses the match and places the test result (true / false) into a test status text file, and the XML portion into another log file.
Continue reading "Continuous Integration with Flex - Part 4" »
So, if you have got this far, your ant build will compile the test harness, which quits after a specified period of time, and then compiles the main build. So far, so good, but it’s not really rocking yet; what we now need to do is get our ANT build to know if our unit tests have actually passed or not (and later down the line by the build monitor). The trick here is to get your swf to somehow output to a textfile that can then be read & understood by the ant build.
Continue reading "Continuous Integration with Flex - Part 3" »
In the next step to CI Nirvana, I'm going to be looking at using ANT to build both our testHarness and the main mxml file. As I mentioned in my previous post, the job we need ANT to do is get it to compile the testHarness, wait for it to close, then compile your main build.
Continue reading "Continuous Integration with Flex - Part 2" »
The first step for getting your CI build up and running will be to get all your basic pieces in place on your local machine.
Some of this stuff (I hope) you will already have in place, but for the sake of being complete I'll include it here...
Continue reading "Continuous Integration with Flex - Part 1" »
The contract I am currently working on is for a large financial institution in Boston. They want to explore new ways of working in our small business unit with the hope that some of our work may make it into the mainstream of the company.
We are not only experimenting with the projects we work on, but also trying out new (for the company at least) ways of working.
So, when my manager came to me late last year and started asking what we could look at next, there was a challenge that I and my workmates (Peter Hall, Ikezi Kamanu and Johannes Nel) had been looking to get our teeth into for a while — Continuous Integration with Flex.
Continue reading "Continuous Integration with Flex - Introduction" »
