[SEDONA-256] R GitHub workflow update #786
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
Update to latest version of actions Replace steps with prepackaged actions: (install java cache, R dependencies and cache) Testing versions (on push to branch and removed matrix)
Test action for build and check bring back matrix
fix typo
Do package checks before installing and compiling Sedona (fail faster)
back to normal behavior, ready for PR
jiayuasu
approved these changes
Mar 5, 2023
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.
Is this PR related to a JIRA ticket?
https://issues.apache.org/jira/projects/SEDONA/issues/SEDONA-256
What changes were proposed in this PR?
Update to the R testing workflow:
Removed cache steps (maven, R packages) already handled by prepackaged actions
Not yet updating to Ubuntu 22.04
How was this patch tested?
On my fork
Did this PR include necessary documentation updates?
No, this PR does not affect any public API so no need to change the docs.