Configure Build Stages for travis CI #870
Merged
Conversation
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
|
💚 |
|
💚 |
petekanev
force-pushed
the
pete/travis-build-stages
branch
from
ffaa639 to
a355b4d
Compare
|
💚 |
petekanev
force-pushed
the
pete/travis-build-stages
branch
from
a355b4d to
0371c47
Compare
|
💚 |
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.
Split the travis configuration into separate jobs in order to receive feedback from PRs a bit quicker on ASBG generator tests, with the package build and runtime tests executing at the end.
The runtime build on PRs should be faster this time around because the runtime android library will be built just once, as opposed to twice (optimized, and regular).