Publish Artifacts to Amazon S3

We run our enterprise version of Team City on an Amazon EC2 instance, which is great for scaling up our build capacity when demand calls for it.  Has a feature where you can configure Team City to publish build artifacts to Amazon S3 buckets ever been considered?  It would be a way to reduce costs for hosting in EC2 and let us use Cloud Front to reduce download times for our developers around the world.  Also because S3 buckets are "infinitely" expandable, it would remove the need for cleaning build artifacts or having to manage server drives when they run out of space.

For now we can script this through MSBuild, but would be great if it was a part of TeamCity's settings.

3 comments
Comment actions Permalink

Peter,

Thanks for the suggestion. This is not yet on our radar. Can you please file a feature request into our tracker for it?
Please also describe where do you envisage the artifacts to be linked from. From TeamCity web UI?
Do you need to store artifacts for all the builds or only for some recent ones?
How is this different from setting up S3 storage on TeamCity server and map .BuildServer/system/artifacts on it?

0
Comment actions Permalink

Is there an open feature request for this functionality?  Or a community plugin that someone has written? I'm porting some builds from Jenkins and CC.NET which upload specific artifacts to S3 as steps in the build.

0
Comment actions Permalink

TW-1558 is the issue to vote and watch.

Thanks

0

Please sign in to leave a comment.