Switch to new Travis CI build environment #867
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- faster VM boot time (running in a docker container) - better performances (linux kernel 3.x instead of 2.x, 4G of RAM instead of 3G, better CPU power/parallelism, faster download, etc.) - Ability to cache files in S3 storage
xuwei-k
added a commit
that referenced
this pull request
Dec 25, 2014
Switch to new Travis CI build environment
|
@xuwei-k thanks for the merge, but ooops, in the meantime I realized that the S3 caching instructions are not optimal (as they are storing far too many things). I'll come up with a fixing PR asap ;) |
gildegoma
added a commit
to gildegoma/scalaz
that referenced
this pull request
Dec 25, 2014
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867.
gildegoma
added a commit
to gildegoma/scalaz
that referenced
this pull request
Dec 25, 2014
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867.
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
xuwei-k
pushed a commit
to xuwei-k/scalaz
that referenced
this pull request
Jan 31, 2015
- store ivy cache - don't store the whole ~/.sbt foldertree in S3 - add a new trick to avoid unnecessary ivy cache uploads Follow up of scalaz#867. (cherry picked from commit 578ebc7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
instead of 3G, better CPU power/parallelism, faster download, etc.)
After file cache being filled, the total build time is reduced from ~6-7 minutes per job to ~5 minutes per job.
See also http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/.