You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
My use case for terrarium is to install my environment faster on Travis CI. Compiling e.g. lxml takes ages and the build would sometimes timeout. With terrarium, builds are four times faster!
I can't provide terrarium pre-built envs for Travis since they use a different architecture. That's why Travis has to build the env and upload it to S3 for later use. However, that doesn't work in pull requests because Travis' secure env var (S3_SECRET_KEY) is not available in pull requests. So a normal branch has to build the envs and upload them.
However, pull requests (if they don't change the requirements) should be able to use the existing pre-built envs on S3. The command crashes without a valid S3_SECRET_KEY and I have to manually download the file and trick terrarium into ignoring the S3_BUCKET env var: here is my .travis.yml config.
Terrarium and Travis CI are a good match and they should work better together. I could even see a terrarium travis command that looks at Travis' env vars and figures out the best strategy to get an env.