Cirrus CI cutbacks ... #3796
Merged
Cirrus CI cutbacks ... #3796
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
|
Administrative merge, since this comes into effect on Sept 1. |
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 missed this, but apparently last month Cirrus CI announced that it is no longer allowing unlimited use for free 😕
https://cirrus-ci.org/blog/2023/07/17/limiting-free-usage-of-cirrus-ci/
Here's our usage over the last few months, measured in "credits". Green is macOS, blue Linux. Our new allowance will be 50 credits per month 😕
So we need to do some serious belt-tightening, esp. wrt to the macOS CI jobs.
So far the changes I propose are:
Meanwhile I restored the Linux ARM CI jobs for 2.13 (JVM) and 3 (JVM, Native). We really do need those ... hopefully they will not be so flaky this time.
Not sure if this is enough. We shall see ...