-
Notifications
You must be signed in to change notification settings - Fork 520
Closed
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.
Description
What would you like to be added:
Adding some retries around failure points in release scripting before failing completely. Eg:
- docker pull commands on the code for Mock Release (Issue Implement clone, commit and push of release notes draft to user's fork #1102 )
- "Step Initial commit of release automation tooling. #1: PUSH GIT OBJECTS (11/14)" (Issue gcbmgr release frequently fails at "push git objects" #933 )
- audit past year's "HACK" and "revert" commits on anago/gcbmgr/lib shell to other points which would benefit from a basic sleep/retry loop
Why is this needed:
In case of failure, often we just need to hack workaround and attempt to re-run the release process, which is very time and resource consuming. Adding retries will allow these attempts to take place on the same run.
Metadata
Metadata
Labels
area/release-engIssues or PRs related to the Release Engineering subprojectIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/critical-urgentHighest priority. Must be actively worked on as someone's top priority right now.Highest priority. Must be actively worked on as someone's top priority right now.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.