I think what you actually want to do here is copy the actual gem into the
build artifacts directory. Cruise guesses that if you copy a directory to
the artifact dir, you mean to show an index file from inside of it.
If you copy the actual gem to the dir, cruise should give you a link to the
actual gem
Jeremy
On Tue, Oct 7, 2008 at 11:50 AM, Byron Appelt <[EMAIL PROTECTED]> wrote:
> I am having a problem with having custom artifacts show up. I have the
> following cruise taks:
>
> task :cruise do
> out = ENV['CC_BUILD_ARTIFACTS']
> mkdir_p out unless File.directory? out if out
>
> rm_rf 'pkg'
> Rake::Task["gem"].invoke
> mv 'pkg', "#{out}" if out
> end
>
> After a build, I can go to command line and see that the gem is getting
> moved into the artifacts directory, and the 'pkg' link does show up in the
> webapp under build artifacts. However, when I click on 'pkg' instead of
> seeing a link to the gem file, I just get a page that says "this should be
> an index of pkg"
>
> What is going on here?
>
> Thanks,
>
> Byron
>
>
> _______________________________________________
> 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
