Disable build dryruns for pushes #367
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
Codecov Report
@@ Coverage Diff @@
## master #367 +/- ##
==========================================
+ Coverage 99.48% 99.54% +0.06%
==========================================
Files 56 56
Lines 3295 3295
==========================================
+ Hits 3278 3280 +2
+ Misses 17 15 -2
Continue to review full report at Codecov.
|
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.
It is unnecessary to run Docker dryrun builds in Drone (builds without pushing to Quay.io) for every push to all branches (especially as a build dryrun is made for PR anyway), and apparently it has the negative consequence of stressing the Drone server and its network leading to timeout errors in the builds.
Even for PRs the build dryruns are a bit questionable, running build&tests would be more meaningful, see #315.