Hi that would be a section in the xsl file
now compile.xsl is used to highlight errors and warnings that's easy to adjust if you want a section there with just time-outs you can find the file in C:\Program Files\CruiseControl.NET\webdashboard\xsl with kind regards Ruben Willems On 7 June 2012 09:16, Matthias Napalowski <[email protected]> wrote: > Thank you! > > or if you want a specific section with time outs only > > > Is there a value to set in the build script? Or do i misunderstand you? > > Regards > Matthias > > > Am 07.06.2012 um 06:42 schrieb Ruben Willems <[email protected]>: > > Hi > > I just made a test project with the batch file as example, and I get the > following > > in the console output : > > [gitnew:ERROR] Command line 'D:\Ontwikkeling\Code\RuWi\CCNet\wait.cmd > localhost' > timed out after 5 seconds. > > --> So that's ok > > > Dashbord Build overview : > > Errors: (1) > > Command line 'D:\Ontwikkeling\Code\RuWi\CCNet\wait.cmd localhost' timed out > after 5 seconds. > > > --> also ok > > > and in the build log there is the following : > > <buildresults> > <message level="Error">Command line > 'D:\Ontwikkeling\Code\RuWi\CCNet\wait.cmd localhost' timed out after 5 > seconds.</message></buildresults> > > > --> also ok > > > > so everything looks ok > > > it is added with level Error, or if you want a specific section with time > outs only, > an xsl that scans for 'timed out after' should also work > > > I tested this with the upcoming 1.7, due in 2 weeks, > http://build.nauck-it.de/download/CruiseControl.NET/ > > http://build.nauck-it.de/download/CruiseControl.NET/1.7.726.8065/ > > > with kind regards > Ruben Willems > > > On 30 May 2012 17:38, Barry Pape <[email protected]> wrote: > >> Sorry for the double post, but I didn't think the first one went >> through. >> >> Any update on this? The recommended batch file looks like a good >> test. >> >> Some additional information on our situation: >> I just moved our builds from version : 1.4.1.3795 where the >> CruiseControl build report would give a message like: >> >> ThoughtWorks.CruiseControl.Core.Tasks.BuilderException: Command Line >> Build timed out (after 7200 seconds) at >> >> ThoughtWorks.CruiseControl.Core.Tasks.ExecutableTask.Run(IIntegrationResult >> result) at >> ThoughtWorks.CruiseControl.Core.Project.RunTasks(IIntegrationResult >> result, IList tasksToRun) at >> ThoughtWorks.CruiseControl.Core.Project.Run(IIntegrationResult result) >> at >> ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult >> result) BaseDirectory: D:\, Executable: C:\Program Files >> \VisBuildPro6\VisBuildCmd.exe >> >> >> to Version : 1.6.7981.1 where the CruiseControl build report gives no >> failure message at all, and we have to search the build log for the >> time out value to see the error. >> >> >> On May 25, 11:08 am, Matthias Napalowski <[email protected]> wrote: >> > maybe with an batch file? >> > --- >> > echo "wait" >> > pause >> > --- >> > >> > this schould execute and wait for a keypress... >> > >> > regards.. >> > >> > 2012/5/25 Ruben Willems <[email protected]> >> > >> > >> > >> > >> > >> > >> > >> > > The patch was applied on the 1.6 release >> > > and the code does look like it should work. >> > >> > > any idea on how I can simulate such a time-out, >> > > so I can simulate the problem. >> > >> > > with kind regards >> > > Ruben Willems >> > >> > > On 24 May 2012 12:22, Matthias Napalowski <[email protected]> >> wrote: >> > >> > >> I would appreciate to have an answer on that question.. >> > >> > >> Thanks! >> > >> Matthias >> > >> > >> 2012/5/22 Barry Pape <[email protected]> >> > >> > >>> I see that this issue has been resolved, and the issue history >> > >>> mentions a patch. Where do I find the patch and how do I apply it? >> > >>> Will it work on Version : 1.6.7981.1? >> > >> > >>> Thanks, >> > >>> Barry >> > >> > >>> On Apr 22, 6:45 am, Ruben Willems <[email protected]> wrote: >> > >>> > Hi >> > >> > >>> > just looked into the source, and indeed, timeouts are not logged >> as >> > >>> warning >> > >>> > / error :-( >> > >>> > so for the moment the only thing that remains is to look for a >> string >> > >>> > 'timed out'. >> > >> > >>> > changing this to an error would make it easier to search for it, >> > >>> > but how would one make the distinguish between a time out and a >> compile >> > >>> > (syntax) error >> > >>> > they're both errors. >> > >> > >>> > made an issue about it : >> http://www.cruisecontrolnet.org/issues/101 >> > >> > >>> > with kind regards >> > >>> > Ruben Willems >> > >> > >>> > On 13 April 2012 15:23, Matthias Napalowski < >> [email protected]> >> > >>> wrote: >> > >> > >>> > > Sorry for my realy late response.. >> > >> > >>> > > The Timeout Message is only a normal Message, no Error or >> Failure. >> > >>> How do >> > >>> > > i get only this Message into the Mail? >> > >>> > > There are a few hundred messages. Wouldnt it more logicaly that >> ccnet >> > >>> > > gives the timeout as a error or fail? >> > >>> > > Regards >> > >>> > > Matthias >> > >>> > > Am 22. Juli 2011 07:58 schrieb Ruben Willems < >> > >>> [email protected]>: >> > >> > >>> > > Hi >> > >> > >>> > >> you'll have to tweak som xsl for this >> > >>> > >> in your ccnet.exe.config or ccservice.exe.config there is a >> section >> > >>> > >> xslFiles >> > >> > >>> > >> these files are used to by the email publisher >> > >>> > >> you can add or remove files as wanted. >> > >> > >>> > >> remember to stop and start ccnet for the changes to take affect >> > >> > >>> > >> with kind regards >> > >>> > >> Ruben Willems >> > >> > >>> > >> On 14 April 2011 10:14, matthias <[email protected]> >> wrote: >> > >> > >>> > >>> hi >> > >> > >>> > >>> how do i get the timeout of an build into the email. >> > >>> > >>> it doesn't show up. >> > >> > >>> > >>> greetings >> > >
