bazel-contrib / bazel-contrib/rules_oci
Add retry field to oci_push and possibly other oci commands
Open
enhancement
help wanted
need: discussion
- Dominant language
- Starlark
- Stars
- 423
- Forks
- 213
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Similar to https://github.com/bazelbuild/rules_docker/issues/1989, oci_push() can sometimes flake due to transient network issues, and retrying would be helpful for mitigating the impact. The current alternative is to retry the whole bazel command
Contributor guide
Research direction
Start by reading the oci_push entry point and checking the other OCI commands to determine which operations could share a retry option. Compare the requested behavior with rules_docker issue 1989; done should include a retry setting that mitigates transient network failures without rerunning the whole Bazel command.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100