Github Action Improvements #503
Merged
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
edwardhartnett
approved these changes
May 6, 2021
…to feature/intel-ci
|
@GeorgeGayno-NOAA or @edwardhartnett can you disable the two |
|
@kgerheiser I have given you admin rights on this repo, so you can set the branch protection. |
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.
Add Intel OneAPI build to CI: Fix #494
Add arguments to print on error for ctest: Fix #501
Add OpenMPI build to CI: Fix #425
Build NetCDf 4.7.4 in CI: Fix #467 and replace #492
Upgrade to Jasper 2.0.25. Jasper 2.0.22 has a known bug with Intel compilers.
Re-name yaml files. I think they were too long and the full name didn't show up in the Github UI.
I have it setup so that all the variants (mac/linux, nceplibs develop/1.3.0, openmpi/mpich) run in the one script, while the other is for Intel. Now this can broken up in a number of ways, but I did it like this to reduce code duplication. Ideally you could use JSON anchors or some other mechanism to re-use steps, but it's not currently possible.