ci: remove shared temp cleanup from tag release workflows #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The current
rc-release.ymldeletes/tmp/bread-ecosystem-ci-*before creating a fresh clone, which can remove another concurrent release job's checkout.release.ymlalso deletes and reuses the fixed/tmp/bread-ecosystem-cipath, which is shared across runner jobs. Use uniquemktempdirectories in these workflows and remove the shared-path deletion. Keep this scoped to breadpaper's release workflow copies. Follow-up to ECO-28.Confirmed the unsafe cleanup on current Forgejo main. Implementation is blocked in this runtime because outbound git SSH is denied:
GIT_SSH_COMMAND='ssh -F /dev/null -o StrictHostKeyChecking=accept-new' git -C /home/breadway/Projects/breadpaper ls-remote origin refs/heads/mainfails withsocket: Operation not permittedto 100.66.238.26:2222. The local PAPER checkout is 16 commits behind main and PAD is 7 commits behind, so I cannot safely base PR branches on current main. MCP provides read-only file access but no branch or push operation. The unsafe paths are identified in the issue body; needs a runtime with Forgejo git push access to make and verify the PR.Implemented in PR #16. Both tag release workflows now use their own
mktempdirectory and clean up only that directory on exit. Verified YAML parsing, embedded shell syntax withbash -n, andgit diff --check.Reviewed PAPER-15 and PR #16. The change meets the requested scope.
Acceptance criteria:
/tmp/bread-ecosystem-ci-*paths. Satisfied by.forgejo/workflows/rc-release.yml:55-58, with clone and index generation using that directory at lines 57-58..forgejo/workflows/release.yml:58-61; clone and index generation both use the unique directory.The EXIT traps clean up each job's own directory even when clone or index generation fails. No automated behavior test was added; the shell/YAML validation recorded on the issue covers syntax, and the changed code paths are straightforward. Current PR head CI is green (
check / check (push)), the PR is mergeable, andgit diff --checkpasses. Looks ready to merge.