search for: cc_build_artifacts

...re ''cucumber/rake/task'' #I have to add this -mischa namespace :features do Cucumber::Rake::Task.new(:all) do |t| t.cucumber_opts = "--format pretty" end Cucumber::Rake::Task.new(:cruise) do |t| t.cucumber_opts = "--format pretty --out=#{ENV[''CC_BUILD_ARTIFACTS'']}/features.txt --format html --out=#{ENV[''CC_BUILD_ARTIFACTS'']}/features.html" t.rcov = true t.rcov_opts = %w{--rails --exclude osx\/objc,gems\/,spec\/} t.rcov_opts << %[-o "#{ENV[''CC_BUILD_ARTIFACTS'']}/features_rcov"]...

...olrb works well now on my XP box but for the following problem: I have set up rails_rcov so that I can generate code coverage automatically at every build. Following the manual, I have a custom task that copies rcov output to a specific folder (d:\work\ccrob\artifacts) I have set up the environment CC_BUILD_ARTIFACTS to /work/ccrob/artifacts using the tip given in another thread about manual build requests. And the result is that there is nothing in the builds about code coverage (when the target folder is actually nicely updated). Anybody has any idea about this? My guess is that ccrb may create links in the...

We''ve just added rspec stories to our CruiseControl.rb build. When there''s a failing scenario we see the failure in the log output, but it doesn''t cause the CruiseControl build to fail. We''ve also just upgraded to the latest rspec version, 1.1.4, which fixes rspec bug 228, but the CC.rb build is still passing. Has anyone got failing rspec stories making