ci(test): delete stale test-release bundles before artifact cleanup#247
Merged
Conversation
Promoted release bundles lock their artifacts in dev-local repos. The cleanup step used jf rt delete with || true, silently swallowing 409s and leaving the paths locked for the next run. Add a step that deletes all versions of test-release in the test project first, so the artifact deletes below it succeed cleanly. Also fix the stale jf rbdell command in the expanded-integration example comment; the correct CLI v2 syntax is release-bundle-delete-local.
Drop ci, refactor, and docs from types-requiring-jira. Those types cover infra tweaks, internal restructuring, and doc updates that do not warrant a Jira ticket. feat and fix remain gated since they represent user-visible changes and bug reports respectively.
alexs-aero
approved these changes
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
test-releaserelease bundles before wiping test repos in the deploy-artifacts integration testjf rbdellcommand in the expanded-integration example comment (correct syntax isjf release-bundle-delete-local)featandfixtypes now require a Jira ticket;ci,refactor, anddocsno longer doWhy
Bundle cleanup: Promoted release bundles lock their artifacts in dev-local repos. JFrog returns 409 on any attempt to overwrite a locked path. The cleanup job used
jf rt delete ... || true, which silently swallowed those 409s and left the paths locked for the next run. The next CI run then failed at deploy time with the same 409. Observed in PR #246 wheretest-release:1.2.9blocked the entire integration test.Test plan