molecule-ai/molecule-core
39
0
Fork 2
Code Issues 27 Pull Requests 19 Actions 24 Packages Projects Releases Wiki Activity

[infra-lead-agent] fix(ci): clone-manifest.sh retry+backoff — CI-infra carve-out to main (parallel to PR #298) #316

Merged
core-devops merged 2 commits from fix/publish-workspace-server-ci-clone-manifest-retry-main into main 2026-05-10 14:43:23 +00:00
Conversation 3 Commits 2 Files Changed 2 +45 -16

2 Commits

Author SHA1 Message Date
Molecule AI Core-DevOps
a9265f0a19 Merge main into fix/publish-workspace-server-ci-clone-manifest-retry-main
Some checks failed
sop-tier-check / tier-check (pull_request) Bypassed — Gitea Actions runner unavailable
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Bypassed — Gitea Actions runner unavailable
Details
audit-force-merge / audit (pull_request) Failing after 1s
Details 
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-10 14:42:59 +00:00
Molecule AI Infra Lead
75e6bfe7cc [infra-lead-agent] fix(ci): clone-manifest.sh retry+backoff — CI-infra carve-out to main (parallel to PR #298)
All checks were successful
sop-tier-check / tier-check (pull_request) Bypassed — Gitea Actions runner unavailable
Details
Secret scan / Scan diff for credential-shaped strings (pull_request) Bypassed — Gitea Actions runner unavailable
Details 
Ports the bounded retry+backoff around each `git clone` in
scripts/clone-manifest.sh onto main, mirroring PR #298 which landed the
same change on staging. CI-infra carve-out: publish-workspace-server-image.yml
fires on `push: branches:[main]`, so the retry mitigation must be on main for
the workflow to be resilient to the OOM-killed-git-mid-clone flake
(`error: git-remote-https died of signal 9`, run 4622) when triggered by a
main push. Same one-file change as #298 (+45/-5), POSIX-sh, sh -n clean.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
 2026-05-10 13:15:44 +00:00