Travis CI: Use declarative style #140
Closed
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
Exact same functionality but done in declarative style which is more compact and easier to understand.
|
Thanks for this @cclauss . This has made our Travis tests comprehensible to me! We normally commit by generating a patch, merging and testing locally, then pushing via hg.python.org/jython . I don't know how to test a CI change without pushing it, but I could see a bit of trial-and-error adjustment would be needed that would make a mess in the commit history. Having done that on a branch of my own fork, I've now committed this PR as f1498dc, and my further adjustments as a345c91, currently being tested by Travis CI. |
|
It's so ,,, green. |
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.
Exact same functionality but done in declarative style which is more compact and easier to understand.