Skip to content
This repository has been archived by the owner on Aug 20, 2019. It is now read-only.

Add cache support to circle #68

Closed
thom8 opened this issue Jan 22, 2016 · 5 comments
Closed

Add cache support to circle #68

thom8 opened this issue Jan 22, 2016 · 5 comments

Comments

@thom8
Copy link
Member

thom8 commented Jan 22, 2016

To speed up test builds.

https://circleci.com/docs/how-cache-works

@AlexSkrypnyk
Copy link
Contributor

@thom8 Could you please outline what would you like to cache from BB

@thom8
Copy link
Member Author

thom8 commented Apr 20, 2016

@alexdesignworks apt packages to begin with but I'd also like to investigate if we could somehow use containers to cache a pre-provisioned build.

@AlexSkrypnyk
Copy link
Contributor

cache a pre-provisioned build.
Do you mean for testing? But how would new changes apply?
I mean, if the box is already provisioned, would you run provisioning again to just provision the changes rather than a whole box from the start?

@thom8
Copy link
Member Author

thom8 commented Apr 21, 2016

For the main project we use CI to replicate an Atlas build (including its minimisation scripts), then test an initial provision with settings from the main projects .beetbox/config.yml.

Therefore we probably want a fresh build for each build but we can cache the APT cache (which will be updated each build) and anything downloaded, as long as version numbers are in the path or name so updates ignore the cache.

However the goal moving forward as mentioned in #151 is to extract most of the roles into their own projects so test coverage can be expanded per project. In this case it would be nice to have a pre-provisioned base image as the sub-projects aren't concerned with the box build but modifications of the current build.

@thom8
Copy link
Member Author

thom8 commented Jun 20, 2016

Cache dir created in #233

@thom8 thom8 closed this as completed Jun 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants