Workaround GitHub Actions time limit
- Dominant language
- C++
- Stars
- 4.4k
- Forks
- 658
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 10
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
### Version
Currently our nightly docker release CI has failed frequently due to reaching to Actions time limit (6 hours).
We need to figure out a workaround to make the CI always success.
### Minimal reproduce step
-
### What did you expect to see?
-
### What did you see instead?
-
### Anything Else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the nightly Docker release GitHub Actions workflow and reviewing which job reaches the six-hour limit. Determine a concrete workaround for the timeout, then verify that the nightly release workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100