we set an environmental variable that you have access to, it's called
CC_BUILD_ARTIFACTS any files you copy into that directory will be accessible
from the build page.
to see a non-trivial example, this is lib/tasks/cruise.rake inside of cruise
which uses rcov and
desc 'Continuous build target'
task :cruise do
out = ENV['CC_BUILD_ARTIFACTS']
mkdir_p out unless File.directory? out if out
ENV['SHOW_ONLY'] = 'models,lib,helpers'
Rake::Task["test:units:rcov"].invoke
mv 'coverage/units', "#{out}/unit test coverage" if out
ENV['SHOW_ONLY'] = 'controllers'
Rake::Task["test:functionals:rcov"].invoke
mv 'coverage/functionals', "#{out}/functional test coverage" if out
Rake::Task["test:integration"].invoke
end
On Feb 6, 2008 1:47 AM, Jyri Vesalainen <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> How do you configure cruisecontrol.rb to leave out some custom artifacts
> like "test.log"?
>
> I'm also wondering what's the best way to include rcov HTML coverage
> reports as custom artifacts?
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> _______________________________________________
> Cruisecontrolrb-users mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
