Force CI to run on runners provided by Github #408
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
provokateurin
force-pushed
the
fix/ci
branch
2 times, most recently
from
43e0444 to
7dddf37
Compare
Signed-off-by: jld3103 <[email protected]>
blizzz
approved these changes
Jun 14, 2023
1 task
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.
Pull Request
Description of the change
CI fails because of the new self-hosted runners. This forces the jobs to run on the runners provided by Github in order to restore working CI. Failure can be seen in #407.
Benefits
CI works again.
Possible drawbacks
Still depends on Github runners so we might have to still wait longer (but it should be still less than before).
Additional information
Checklist
Chart.yamlaccording to semver.