ci: reduce cache conflict and usage#7642
Conversation
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }} | ||
| group: binding_c-${{ github.ref }}-${{ github.event_name }} |
There was a problem hiding this comment.
Why this change? Isn't it identical?
There was a problem hiding this comment.
I want to share the same concurrency group with .github/workflows/test_behavior_binding_c.yml.
Each binding shares the same concurrency group. If there are multiple workflows for a binding, these workflows will run in sequence.
There was a problem hiding this comment.
Rollbacked. Tweaking concurrency groups brought more troubles than its worth.
Xuanwo
left a comment
There was a problem hiding this comment.
Thanks a lot for working on this! Only one concern.
| --silent \ | ||
| --show-error \ | ||
| --fail \ | ||
| https://dlcdn.apache.org/hadoop/common/hadoop-3.3.5/hadoop-3.3.5.tar.gz | tar \ |
There was a problem hiding this comment.
We need this cache. ASF's CDN is slow and unstable.
|
🤯 |
|
Hey, I want to test docker and cache approach. Now it's rollback to cache approach. Test:
Looks comparable. If we want to save GitHub Action cache quota, it's fine to switch to Docker which is free of charge thanks to Docker policy. Logs: docker pull apache/hadoop:3.3.5 logscache logs |
Which issue does this PR close?
None.
Rationale for this change
Reduce cache conflict among jobs.
What changes are included in this PR?
Are there any user-facing changes?
None
AI Usage Statement
No.