Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add remote cache implementation #80

Closed
vmrob opened this issue Jul 18, 2016 · 2 comments
Closed

Add remote cache implementation #80

vmrob opened this issue Jul 18, 2016 · 2 comments
Labels

Comments

@vmrob
Copy link
Contributor

vmrob commented Jul 18, 2016

Needy should be able to publish built artifacts to s3 and should probably use a redis server to implement the required file locking. Additionally, needy should support lock-free read-only of the same s3 cache.

The use case here is that if a development team has a ci server they wouldn't mind receiving pre-built artifacts from, they could have read-only access to the s3 cache for published artifacts while the ci server provides those artifacts to s3.

@ccbrown
Copy link
Owner

ccbrown commented Jul 18, 2016

I'm going to rename this from "Add s3 cache support" to "Add remote cache implementation". I want the functionality, but I want to evaluate whether s3+locking server is the best solution.

@ccbrown ccbrown changed the title Add s3 cache support Add remote cache implementation Jul 18, 2016
@ccbrown
Copy link
Owner

ccbrown commented Aug 12, 2016

Merged into #108

@ccbrown ccbrown closed this as completed Aug 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants