ci(refactor): extract build setup logic into setup-build #622
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 patch extracts the build setup logic into a composite action called
setup-build
to avoid repeating similar steps in different jobs. The setup process includes installing dependencies and libraries, extracting tarballs, runningautoreconf
, and executingconfigure
.In the future, if we need to elaborate further on setting up libraries (including building and caching), such as MPI or FLINT, we can manage them all in one place.
There are several ways to organize shared logic in GitHub Actions:
setup-build
needs to modify$LIBRARY_PATH
etc.)This patch adopts the last option. To mitigate the drawback, I added lines like
### Initialize setup ###
in therun:
field, which will appear in the logs.