[JIRA] Commented: (CC-800) Dashboard view does not represent succesful builds

    [ http://jira.public.thoughtworks.org/browse/CC-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_19076 ] 

David Biesack commented on CC-800:
----------------------------------

Paul Willworth send the following message in response to my inquiry on the CC mailing list

Something to try is when you start up cruise control, use the -dashboardurl command line option, so just add -dashboardurl http://myhost:8080/dashboard to the end of the command that starts up the build loop, cruisecontrol.sh.  Normally this isn't necessary, but I had to do it because I am using customized port numbers on a couple things, and I experienced the same symptom.

I have not tried this, but I include this here in case others stumble upon this ticket.

> Dashboard view does not represent succesful builds
> --------------------------------------------------
>
>                 Key: CC-800
>                 URL: http://jira.public.thoughtworks.org/browse/CC-800
>             Project: CruiseControl
>          Issue Type: Bug
>          Components: Dashboard
>    Affects Versions: 2.7.2
>         Environment: Win32
>            Reporter: John Prause
>            Priority: Major
>         Attachments: cruisecontrol.log, gray_build1.jpg, gray_build2.jpg
>
>
> In 2.7.1, the dashboard represented successful builds with Green indicators. Using 2.7.2, this is no longer the case, the successful builds now show a gray indicator. It also shows that the build was successful but that the build is discontinued. I will attach screenshot.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb