Craig, WOW!!!!
This is exactly what I had hoped for. I cannot praise you enough for the information that is provided on this page. For me I think there was a gap in the CCNET documentation and I certainly think you have more than filled it!. I have a couple of comments from my perpective that would help me and other newbies. 1) I would like to make (and would like confirmation on my understanding) related to actionName. Originally, I thought that this was some sort of "function" call to the plugin (i.e. this action existed in the plugin and the name had to be matched. However, my understanding now is that it is a _user_ defined string that does not have to match any existing string in the plugin - the only limitation is that it has to be unique. Correct me if I am wrog. 2) Another very important thing that I am still not fully aware of is when the *.config file is re-read. So when people are debugging or modifying the dashboard.config file, how can these updates be reflected in the webpage. I have found the information in this link to be very useful:- http://www.distribucon.com/blog/CruiseControlNETDashboardModifications.aspx CruiseControl.NET Dashboard Modifications "When customizing the appearance of the CC.NET Web Dashboard, you often need to modify the file c:\Program Files\CruiseControl.NET \webdashboard\dashboard.config. However, you won't see the changes you make there reflected back in the browser until that file is reloaded. The easiest way to reload dashboard.config is to quickly modify web.config (add a space and delete it), and save. This forces IIS to reload the web application, which in turn causes dashboard.config to give up it's new settings. This is especially useful in a hosted environment where you don't have access to administration-level tools. An alternative would be to just bounce the entire web server by stopping and starting the service, but that's not always feasible nor practical." Again many, many thanks for this information! Liam On Jun 10, 12:01 pm, "Craig & Sammi Sutherland" <[email protected]> wrote: > Hi Liam, > > I have put together a quick post on the parts of the dashboard for > you:http://csut017.wordpress.com/2009/06/10/inner-workings-the-anatomy-of... > shboard/. > > Let me know if anything is unclear. If there are no issues with it, I'll > look into getting it put into the documentation sometime (but that'll take > more work, hence the blog post first!) > > Craig > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of LiamD > Sent: Wednesday, 10 June 2009 10:19 a.m. > To: ccnet-user > Subject: [ccnet-user] Webdashboard and Plugin display location > > I have tried to find a general description of the webdashboard, with > the CCNET documentation being the > besthttp://confluence.public.thoughtworks.org/display/CCNET/Web+Dashboard > > However, I am still trying to understand how the various plugins > (especially Project and Build plugins) are displayed on the screen. > There seems to be 2 regions the left hand region and the main > display. > > So using this example, how do I know where the following snippets are > to be displayed - on the left or main sections of the dashboard: > > <buildReportBuildPlugin> > <xslFileNames> > <xslFile>xsl\header.xsl</xslFile> > <xslFile>xsl\compile.xsl</xslFile> > <xslFile>xsl\unittests.xsl</xslFile> > <xslFile>xsl\modifications.xsl</xslFile> > <xslFile>xsl\fxcop-summary.xsl</xslFile> > </xslFileNames> > </buildReportBuildPlugin> > <xslReportBuildPlugin description="NUnit Details" > actionName="NUnitDetailsBuildReport" xslFileName="xsl\tests.xsl" /> > > It is never really explicitly stated anywhere in documentation that I > have reading. I have never seen a diagram that shows the varions > regions of the dashboard display nor a description of what the regions > will be used for. If anyone can give guidance it would be appreciated. > > Thanks, > Liam
