From 25b21c88cba13fb6218d37ff567d595d83c476e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Caio=20Rom=C3=A3o?= Date: Fri, 16 Apr 2010 17:28:24 -0300 Subject: [PATCH] Fixing typo on manual.red. CC_BUILD_ARTIFACTS is misspelled - the "I" from ARTIFACTS is missing. This patch fixes that. --- app/views/documentation/manual.red | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/app/views/documentation/manual.red b/app/views/documentation/manual.red index 046eb7c..bcc6459 100644 --- a/app/views/documentation/manual.red +++ b/app/views/documentation/manual.red @@ -156,7 +156,7 @@ p(hint). Hint: You cannot set both the rake_task and build_co h1. What should I do with custom build artifacts? Some build tasks generate custom output, like test coverage statistics, that you may want to keep and see on the build page. -CruiseControl.rb supports the integration of that output by setting the CC_BUILD_ARTFACTS environment variable +CruiseControl.rb supports the integration of that output by setting the CC_BUILD_ARTIFACTS environment variable to a directory that's been set aside specifically to collect them. If you ensure that your special task writes its output to that directory or a subdirectory of it, then the resulting build artifacts page will automatically include links to every file or subdirectory found in the build artifacts directory. -- 1.7.0.5