search

travis-ci / artifacts

Travis CI Artifacts Uploader
MIT License
87 stars 25 forks source link

Explain differences with Dpl #14

Closed thedrow closed 10 years ago

thedrow commented 10 years ago

Dpl can also upload artifacts to S3 & Github Releases. Maybe those implementations should move here instead?

Joshua-Anderson commented 10 years ago

As the author of both of those providers, think that would be a good idea. I can deprecate the s3 provider when this is released.

joshk commented 10 years ago

I don't think this tool contends with DPL S3 support at all.

This is a replacement to travis-artifacts.

And to be fair, it may not be used for a long period of time as we have something bigger planned in terms of artifact uploads (eg. in the UI)

Joshua-Anderson commented 10 years ago

So the purpose of this is to upload build binaries where the purpose of dpl s3 support is for deploying to s3 webpages?

joshk commented 10 years ago

This is for build binaries, mysql logs, postgres logs, coverage reports etc.

This is not meant for websites.

thedrow commented 10 years ago

Got it! I forgot that there are usecases for both :P

meatballhat commented 10 years ago

@thedrow I'm closing this down for now. Please yell if that's the wrong move! :smiley_cat: