Problems with Jetty/Dashboard When Installing from Sources.

I've been experimenting with Cruise Control. I was able to download the
cruisecontrol-bin-2.8.2.zip and install it on Linux. I was able to configure
my project to update from svn correctly, build and run checkstyle. The next
thing I wanted to do was add the checkstyle page to the web application. I
tried following instructions for rebuilding the web application but I
discovered that I needed files which were only in the source distribution
and started working towards reinstalling from sources. However, I have not
had much luck getting CC working from sources...

== What I have tried ==
I used
http://confluence.public.thoughtworks.org/display/CC/Getting+Started+With+CruiseControlas
a guide.

I checked out the 2.8.2 tag to /opt/cruisecontrol-2.8.2. I was able to
successfully run the main/build.sh script and had it complete without
errors. I then ran main/bin/cruisecontrol.sh and verified that it complained
about not having a config.xml. So far everything is okay.

I then created a /home/cruisecontrol with projects, logs and artifacts
subdirectories. I checked out my project under projects (it has the
build.xml in it) and created a /home/cruisecontrol/config.xml with my
project in it.

BTW: All of these files and directories are owned by
cruisecontrol:cruisecontrol.

The wiki page was not specific about how to start cruise control in step 6.
When I installed cruise control from binaries I created an
/etc/init.d/cruisecontrol script as described in
http://confluence.public.thoughtworks.org/display/CC/RunningCruiseControlFromUnixInit.
It worked well when then so it seemed likely to work again. I modified that
the user configuration in that script to point CC_INSTALL_DIR to
/opt/cruisecontrol-2.8.2 and CC_WORK_DIR to /home/cruisecontrol. I then
tried restarting CC using the /etc/init.d/cruisecontrol script and the fun
begins... This is point that I am fairly certain the train left the tracks
;-)

There was a series of files and directories which are not where they were
expected. I experimented with adding links but it is pretty clear that I am
just adding hacks. I did eventually get the build loop working. I then was
able to build the war file for the web application but could not get
dashport to come up because cruisecontrol could not find jetty. I could have
added more links but I am pretty convinced the developers envisioned
something a lot cleaner than this.  :-)

How is cruise control supposed to be started when build from an svn
checkout? Are there additional build steps that I missed?

Thanks for your the time and help.

-Brian

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user