aspose file tools*
The moose likes Ant, Maven and Other Build Tools and the fly likes How to run CruiseControl dashboard on port other than 8080 with embeded Jetty? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "How to run CruiseControl dashboard on port other than 8080 with embeded Jetty?" Watch "How to run CruiseControl dashboard on port other than 8080 with embeded Jetty?" New topic
Author

How to run CruiseControl dashboard on port other than 8080 with embeded Jetty?

Riffle Chris
Greenhorn

Joined: Feb 18, 2009
Posts: 27
Hi everyone,

Is it possible to run CC and view the dashboard webapp on a port other than 8080?

I edited [cc_home]/wrapper.conf and set wrapper.app.parameter.3 to the desired port (ex: 8087)

I edited [cc_home]/etc/jetty.xml and set the addConnector section with this:
<Set name="port"><SystemProperty name="jetty.port" default="8087"/></Set>

I get this error in my logs: [cc]Jul-14 09:48:43 atusReportTask- Failed to reach dashboard instance : http://localhost:8080/dashboard/buildloop/listener, either the dashboard has not started up or there is a network problem.

? How is it printing an output error message looking for port 8080 when I've set properties for a different port? Was it compiled with java code that uses 8080 that is ending up in the error message?

|--> maybe it's related to this?: --> http://jira.public.thoughtworks.org/browse/CC-766

I can see the dashboard in my browser at http://localhost:8087/dashboard, but all my projects are "grayed out" (instead of green) The CC docs say that grey projects on the dasboard: indicates an inactive or discontinued project*.

* Inactive projects are ones that are defined in CruiseControl's configuration file but have never been built (in other words, CruiseControl can't find any logs corresponding to this project). A discontinued build is one that has log files from previous builds, but is not defined in CruiseControl's configuration file

I also tried running running the cruisecontrol.bat from the command line and specifying the options: webport and -dashboardurl to which I get the same result(that same exception and greyed out projects on my dashboard)

I'm running Dell Lattitude WinXP 32 bit w/Intel Celluron Duo and Java 1.6u14


Thanks for any help!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: How to run CruiseControl dashboard on port other than 8080 with embeded Jetty?
 
Similar Threads
Setting up Cruise Control with SVN and Ant
Experiences with Maven?
Journal Article - Driving On CruiseControl - Part 1
problems with vss in cruisecontrol
Cruise Control config xml problem