travis-ci: try harder to fix deploy #1906
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
Problem: the previous fix for travis-ci auto-deploy was broken because the deploy was being attempted on a builder that doesn't run `make distcheck` any more, so there was no tarball to deploy. Move the deploy to a builder with DISTCHECK=t.
|
NP at all! Glad you're working on this one. Will press button once this one passes. |
Codecov Report
@@ Coverage Diff @@
## master #1906 +/- ##
=========================================
- Coverage 80.14% 80.1% -0.05%
=========================================
Files 196 196
Lines 35065 35065
=========================================
- Hits 28104 28089 -15
- Misses 6961 6976 +15
|
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.
I apologize, but I put the GitHub deploy into the wrong travis builder (it doesn't run make distcheck, so there was no tarball to deploy).
I've tested this now as best I could on my own branch, and I believe it should be fixed this time.
Really sorry about the extra noise!