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.
This pr contains a few changes to the CI that should bring a decent reduction in overal CI runner load.
Potential further improvements
I could move tools/odbc and tools/jdbc into separate yml files and add similar optimization to only run the relevant ci for those directories. I could also add this to this PR?
For more drastic changes in CI runner load we could consider running the CI only on a specific subset pull_request events. For example we could only run the CI on the pull_request.opened and and pull_request.review_requested events (see github docs), which would mean that CI will run automatically on the initial pr open, but for the ci to be rerun when the author has made changes, the author has to explicitly request a review, which will then trigger the CI. However, whether this is a development workflow we want is up for discussion. I'd say it makes sense to wait out this pr and see if CI queue/run times improve enough to leave it as is.