This repository was archived by the owner on Jul 22, 2020. It is now read-only.
Conversation
Split each test target into a dedicated job, add docker build tests
prymitive
force-pushed
the
travis-build-stages
branch
from
4759e04 to
5b18d6b
Compare
terinjokes
approved these changes
Dec 4, 2017
Merged
Contributor
Author
|
This went to wrong branch, redo in #199 |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Split up all tasks run on Travis CI into stages.
This slows down CI jobs (~3m -> ~6m), but isolates different tests and makes it more obvious what failed.
Isolating jobs allows to add new jobs easily, like doing a test build of a docker image, which now happens (and slows things down even more, with extra 4m more needed).