kou commented on PR #13556:
URL: https://github.com/apache/arrow/pull/13556#issuecomment-1180019956
We want to use `sccache` because we can't use `actions/cache` of GitHub
Actions with our "one branch per task" approach, right?
Can we change our approach so that we can use `actions/cache`? For example:
1. We always use the `master` branch for all tasks instead of creating one
branch per task
2. We add `jobs/${JOB_ID}/tasks.yaml` (or something) that lists commit IDs
for target tasks instead of using branch search feature of GitHub (that is too
slow for many branches)
(We can keep only the latest N jobs because old logs in GitHub Actions
are removed.)
3. We create a `${JOB_ID}-${TASK_NAME}` tag for each commit of task to
create a release of GitHub Releases to upload artifacts
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
