Skip to content

feat(release): re-run failed QA lanes from the QA step - #18

Merged
rjd15372 merged 1 commit into
mainfrom
feat/rerun-qa-lanes
Nov 13, 2026
Merged

rjd15372 merged 1 commit into
mainfrom
feat/rerun-qa-lanes

Conversation

@rjd15372

Copy link
Copy Markdown
Collaborator

What

Once QA has finished, the QA step of the release wizard offers:

  • a Re-run button on each failed lane, and
  • a Re-run all failed button for the step.

Both ask for confirmation. The dashboard then asks GitHub to run the job (or every failed job) again on the same QA run. Passed lanes keep their result, QA goes back to running, and the buttons return when it finishes again.

Details

  • GitHub accepts a job re-run only once the whole run has completed, so the buttons show only when QA is finished.
  • New action POST /api/release/releases/{id}/rerun-qa with {head, lane}; an empty lane means every failed lane.
  • Each re-run is written to the audit log (rerun_qa, the lanes as detail). No PR comment.
  • A one-minute cooldown per release, as for the other retries.

Tests

Backend: the action (one lane, all, refusals, GitHub error, cooldown) and the two client requests. Frontend: buttons, dialogs and when they show.

Once QA has finished, each failed lane has a Re-run button and the step
has a Re-run all failed button. Both ask for confirmation, then run the
jobs again on the same QA run. The re-run is written to the audit log.

Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>
@rjd15372
rjd15372 merged commit 5fc9799 into main Nov 13, 2026
5 checks passed
@rjd15372
rjd15372 deleted the feat/rerun-qa-lanes branch November 13, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant