Repository navigation
feat(release): re-run failed QA lanes from the QA step - #18
Merged
Merged
Conversation
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>
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
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.
What
Once QA has finished, the QA step of the release wizard offers:
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
POST /api/release/releases/{id}/rerun-qawith{head, lane}; an empty lane means every failed lane.rerun_qa, the lanes as detail). No PR comment.Tests
Backend: the action (one lane, all, refusals, GitHub error, cooldown) and the two client requests. Frontend: buttons, dialogs and when they show.