Re: Usinng different XSL files for different projects
Venkata Mulpuru <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Guys, On Tue, Feb 3, 2009 at 6:51 PM, Venkata Mulpuru <[email protected]> wrote: > Hello All, > > Question 1 > I am running an instance of cruisecontrol and dashboard server on one > of the machines (say dashboard-server) and use two other machines (say > project1-server, project2-server) to run cruisecontrol and send their > build results to the main dashboard (The approach described in the > website). > > The project1-server is running junit tests on a project and > project2-server is running embedded unit tests. The test results > format in xml is different for both the projects. I have the XSL file > that works for embedded unit tests and can place it in the > webapps/cruisecontrol/xsl folder. > > The problem is when I do this, the junit tests don't show up in the > cruisecontrol build results page for project1. Is there any way I can > specify different XSL files for different projects all reporting to a > central dashboard/cruisecontrol server? I found a work around for this. When the build completes, you can use the <execute> plugin inside <publishers> and call wget to access the buildresults and testdetails webpages from the localhost. This would then generate caches of the html files in the shared log directory. >From then on, when the same pages are accessed from the main dashboard server, they will show up with proper xsl for different projects. Hope this helps someone. > > Question 2 > How do I run just the instance of dashboard server and not > cruisecontrol/dashboard combination? I want to do this and have my > different cruisecontrol instances report to the dashboard server. I still did not figure this out. > > Thanks for any help. > > - > Manoj > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H