Notify Investigator when FB Tests goes red on a PR - #4511
Open
travagliad wants to merge 1 commit into
Open
Conversation
Adds .github/workflows/notify-investigator.yml, mirroring the workflow of the same name in percona/pmm-qa. It fires the Investigator Claude Code Routine with this repo's PR number and the failed run URL, so Investigator can pick up an FB Tests failure the same way it already picks up pmm-qa's own scheduled CI failures. FB Tests is a native GitHub Actions workflow here, dispatched per feature build by Jenkins, so workflow_run is the right event -- no status or check_run listener is needed. Requires an INVESTIGATOR_ROUTINE_TOKEN repo secret before it can fire. Signed-off-by: Claude <noreply@anthropic.com>
Collaborator
|
Server docker: perconalab/pmm-server-fb:PR-4511-2a1eca0 |
Collaborator
|
API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6946/ |
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
3 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.
https://jira.percona.com/browse/PMM-0
What
Adds
.github/workflows/notify-investigator.yml, firing the Investigator Claude Code Routine (trig_01FhHBdz2yBibyVEfnG5gbQz) whenever FB Tests completes withconclusion: failureon a PR in this repo, passing the PR number and failed run URL. Mirrorspercona/pmm-qa's workflow of the same name.FB Tests is confirmed to be a native GitHub Actions workflow in this repo (
.github/workflows/pmm-qa-fb-checks.yml) — Jenkins only dispatches it viaworkflow_dispatch; it doesn't post the results itself. Soworkflow_runis the correct event, same as pmm-qa's version, and nostatus/check_runlistener is needed.The PR number normally comes from
github.event.workflow_run.pull_requests[0].number, with a head-SHA lookup fallback for the rare case where that PR has since closed; if neither resolves, the job logs a notice and notifies nobody instead of firing with nothing to investigate.Why
Investigator's second event source (FB Tests going red) has no notifier yet — this closes that gap so pmm-submodules failures reach Investigator the same way pmm-qa's own CI failures already do.
INVESTIGATOR_ROUTINE_TOKENsecret (same bearer token value as pmm-qa's, added separately since secrets aren't shared across repos/orgs). Not part of this PR. Until it's added, the job fails loudly with an::error::naming the missing secret rather than silently no-op'ing.