Enhance after_success for Travis CI #280
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
Use default bash if-then-else block with semicolon after each command and fix spelling for "incompatibility". Don't do `mvn clean` b/c we need the test results for the following tasks and don't need to rebuild everything.
sepe81
force-pushed
the
travis-after_success
branch
from
9414332
to
352f509
Compare
|
@lukaszlenart the api key for UpdateImpact seems to be ignored. At the end of the relevant Travis CI build I see Edit: Maybe this just works for |
sepe81
commented
Nov 21, 2018
|
@sepe81 we can ignore the UpdateImpact plugin, I mostly added it to have a badge with number of dependencies ;-) |
|
osm! about two minutes save in jdk8 job, thanks a lot! |
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.
Use default bash if-then-else block with semicolon after each command and fix spelling for "incompatibility".
Don't do
mvn cleanb/c we need the test results for the following tasks and don't need to rebuild everything.