Update Linux build matrix and Readme on supported OSes and Libraries #5991
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.
Purpose and Motivation
This is a GitHub Actions maintenance PR, combined with documentation update.
I updated README.md to reflect, more or less, our platform support guarantees, based on the build environment in GitHub Actions and information I came across on the forum and in the PRs in the last few months, with the exception of the following:
Notes on supported GCC and Clang versions:
libstd++
for clang6.0 on Ubuntu 20.04 (and Ubuntu 18.04 image is deprecated).I've also made one (possibly?) considerable change to the GHA workflow: I made it automatically run weekly, on top of the previous behavior (run on push, PR, tags etc). This will happen on the default
develop
branch. Now that we merge things into develop less frequently, there's often the case where it takes more than one week between builds ondevelop
, which makes the caches expire. New PRs and pushes will use cache from the default branch, but if it expires, it's not available. This causes longer build times for new pushes and PRs after a break. With this addition, hopefully, we'll always have an up-to-date cache so that new PRs will be built quicker, even in periods of low activity for the project. The downside is that we add this automatic weekly build, which is otherwise unnecessary, except for renewing the cache.Types of changes
To-do list