-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade github actions #1398
Upgrade github actions #1398
Conversation
GitHub appears to have intermittent access issues when running a dap2 test against iridl.ldeo.columbia.edu (see Unidata#1396 (comment)). Disable this specific test for pull requests, but still run locally and on jenkins. Also, they have upgraded their server to support https, so we will use that in the test.
a9fbec4
to
02b5072
Compare
@DennisHeimbigner - would you like to remain in the CODEOWNERS file? It's currently setup to automatically tag you as a reviewer for changes made to anything living under |
If I am useful in that role, then yes. But I will defer to Ward about this. |
And of course defer to you about the Java repositories. I am ok either way. |
Thank you Dennis! I'd love to keep you in the loop on the dap2/dap4/netcdf4/httpservices netCDF-Java modules as long as you are willing (and if at any point the notifications become too much, just let me know!) The only dap2 related change is this PR is to disable a test that hits iridl.ldeo.columbia.edu, as I have noticed over the years that github periodically has trouble reaching the site (the test will still be run as part of other testing workflows, just not GitHub pull requests). |
If memory serves, may years ago, Columbia was running a fork of the OPeNDAP Hyrax DAP2 server. |
It looks like that is still the case (InGrid Docs). |
Sigh! Oh well. |
Description of Changes
GitHub is closing down
actions/cache
v1
andv2
, and this PR bumps us to the latest (v4
). This also bumpsactions/setup-java
to the latest version (v4
).Also, disable the dap2 test that hits iridl.ldeo.columbia.edu (see #1396 (comment)) when testing PRs, and update the CODEOWNERS file.
PR Checklist
until ready for review