Raible's Wiki

Raible Designs
Wiki Home
News
Recent Changes

AppFuse

Homepage
  - Korean
  - Chinese
  - Italian
  - Japanese

QuickStart Guide
  - Chinese
  - French
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish
  - Japanese

User Guide
  - Korean
  - Chinese

Tutorials
  - Chinese
  - German
  - Italian
  - Korean
  - Portuguese
  - Spanish

FAQ
  - Korean

Latest Downloads

Other Applications

Struts Resume
Security Example
Struts Menu

Set your name in
UserPreferences


Referenced by
AppFuseSupport
Articles
Articles_cn
Articles_de
Articles_pt
Articles_zh




JSPWiki v2.2.33

[RSS]


Hide Menu

AppFuseCruiseControl


This is version 2. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]


I tried several times to get AppFuse to work with CruiseControl, but never got it to work. Rather than just throwing away my efforts, I figured I'd document them here in hopes that someone else might be able to figure out a solution.

To setup automated builds with CruiseControl and AppFuse, you need to download CruiseControl (I used 2.2.rc3). Extract it to your $TOOLS_HOME directory, wherever that may be. I believe you have to build it too (with Ant).

After you've installed and built CruiseControl, create an "appfuse-cc" or similar directory next to your project directory. In my tests, I had:

c:\Source
c:\Source\appfuse
c:\Source\appfuse-cc

Download the following files and put them in the "appfuse-cc" directory:

To begin, you'll need to create a "logs/appfuse" directory in the "appfuse-cc" directory and you'll also need to run "ant" to run everything manually once. I'd love to automate these steps, but I couldn't figure out how.

I used Cygwin to run cruise.sh. You'll likely need to change paths in the above files to match your system.

I experienced many issues in the process of trying to get this to work. You can't use the simple <ant> builder with AppFuse b/c it doesn't find all of the tasks (even though they're defined) in build.xml. To get around this, you have to use the antscript attribute - which works, but the process hangs after running all the tests. It just sits at:

BUILD SUCCESSFUL
Total time: 3 minutes 39 seconds

... for hours ...

So this is where I'm at, everything works from a build/test perspective, but CC won't recover after running the antscript and just hangs. If I specify a timeout - it'll hit the timeout and then publish the results as failed (even though everything succeeded).


Attachments:
config.xml Info on config.xml 1692 bytes
build.xml Info on build.xml 1251 bytes


Go to top   More info...   Attach file...
This particular version was published on 06-Nov-2006 13:52:22 MST by MattRaible.