[
https://issues.apache.org/jira/browse/SEDONA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696372#comment-17696372
]
Jia Yu commented on SEDONA-256:
-------------------------------
Your suggestions make sense to me but I feel it is quite challenging to get
everything right. May be you can break it to several PRs? Let's start with some
simple fixes:
* Update to latest versions of actions
** for example, the latest setup-java seems to handle caching maven jars
without that extra step
* Fix deprecated features (set-output etc.)
* Use already made and maintained actions, e.g. setup-r-dependencies to
install and cache r dependencies
Then we move on to
* Update to latest Ubuntu (18.04 is said be deprecated soon)
Then
* Chain workflows: have one action build Sedona jars, and then run other
actions based on these jars (right now all workflows build their own jars)
> Upgrade GitHub workflows
> ------------------------
>
> Key: SEDONA-256
> URL: https://issues.apache.org/jira/browse/SEDONA-256
> Project: Apache Sedona
> Issue Type: Improvement
> Reporter: Gregoire Leleu
> Priority: Major
>
> Some improvement could speed up GitHub workflows (and save compute):
> * Chain workflows: have one action build Sedona jars, and then run other
> actions based on these jars (right now all workflows build their own jars)
> * Update to latest versions of actions
> ** for example, the latest setup-java seems to handle caching maven jars
> without that extra step
> * Fix deprecated features (set-output etc.)
> * Use already made and maintained actions, e.g. setup-r-dependencies to
> install and cache r dependencies
> * Update to latest Ubuntu (18.04 is said be deprecated soon)
> Not sure what is the best way to work on this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
