An alternative that is not as professional, but takes less effort: 1. Include your (project-specific) link to your release directory as a ExternalLink in your project's ccnet config file. 2. Train your users to click on the webdashboard link that is already in the existing build notification emails, and then from there they can see/follow the link to your release directory.
Not as professional because it means two clicks instead of one, and requires minor user training. Easier because its a one-line config change and doesn't require messing around with XSL and XML outputs. Personally I think its a good idea to include your release directory as an ExternalLink anyway (along with links to documentation, test/production environments, etc.), even if you do go down the XSL route. Cheers, - Sam. On Mon, Feb 2, 2009 at 5:34 AM, Ruben Willems <[email protected]>wrote: > Hi > > > in your build script : echo out this folder > in Nant it would be : > <echo message="TheRealBuildFolder is located at : ${RealBuildFolder}" /> > > so this line is now in the result file > now you can use an xsl file to search for it, and it can be included in the > email. > > > with kind regards > Ruben Willems > > > On Mon, Feb 2, 2009 at 12:30 PM, Nikhil <[email protected]> wrote: > >> >> My company copies the build output to a shared location and the >> location should then be shared with all concerned Dev and QA. This >> location is project specific and thus needs to be read from some >> variable. >> >> Could not find any thing of this sort to add text in the email >> publisher or any xsl file. Is there any way to handle this? > > >
