Adopt Apache Magpie (agent-assisted maintainer workflows) + JMeter config#1
Draft
milamberspace wants to merge 5 commits into
Draft
Adopt Apache Magpie (agent-assisted maintainer workflows) + JMeter config#1milamberspace wants to merge 5 commits into
milamberspace wants to merge 5 commits into
Conversation
Complete the snapshot-based adoption started in 729551e: - Pin the framework in .apache-magpie.lock (git-branch, apache/magpie@main) - Wire security, pr-management, and issue skill families (+ always-on setup-*/list-*) as gitignored magpie-* symlinks - Scaffold .apache-magpie-overrides/ - Wire the agent-guard PreToolUse hook in .claude/settings.json - Document the adoption in README.md and AGENTS.md Generated-by: Claude Opus 4.8
Add .apache-magpie-overrides/project.md — the per-project config the apache-magpie skills read to resolve identity, repositories, mailing lists, mail sources, and security-workflow knobs for JMeter. Filled from confirmed facts (upstream apache/jmeter@master, GitHub Issues, dev@/private@/user@/commits@jmeter.apache.org, ASF Vulnogram CNA, Gmail+PonyMail mail sources). Security-tracker/board/issue-template blocks are marked N/A: JMeter runs no dedicated GitHub security tracker (.asf.yaml projects: false); vulnerabilities go to security@apache.org and private@jmeter.apache.org. Generated-by: Claude Opus 4.8
Add the three per-project config files the pr-management-triage skill reads from .apache-magpie-overrides/: - pr-management-config.md — identifiers, labels, grace windows (tuned longer than framework defaults for JMeter's slow triage cadence), workflow choices (pr-body feedback channel). - pr-management-triage-comment-templates.md — JMeter doc URLs (CONTRIBUTING.md, gradle.md, building.html), the fixed quality-criteria marker, and the AI-attribution footer. - pr-management-triage-ci-check-map.md — maps JMeter's real GitHub Actions check names (Validation, Error Prone, Matrix Preparation, the JDK x vendor x OS x locale test matrix) to categories + gradle.md. area-grouping is disabled (JMeter uses no area:* labels); the workflow labels are documented as not-yet-created (PMC decision) so label actions degrade to feedback-only until then. Generated-by: Claude Opus 4.8
Match the SPDX-License-Identifier header the four sibling files in .apache-magpie-overrides/ already carry (project.md, pr-management-config.md, pr-management-triage-comment-templates.md, pr-management-triage-ci-check-map.md). AGENTS.md is intentionally left without a header, consistent with JMeter's other root docs (README.md, CONTRIBUTING.md, SECURITY.md, THREAT_MODEL.md, gradle.md), which carry none. Generated-by: Claude Opus 4.8
vlsi
reviewed
Jul 7, 2026
| "hooks": [ | ||
| { | ||
| "type": "command", | ||
| "command": "python3 \"$CLAUDE_PROJECT_DIR/.claude/hooks/agent-guard.py\"", |
There was a problem hiding this comment.
What is this? Why creating a hook without agent-guard.py?
vlsi
reviewed
Jul 7, 2026
| <!-- SPDX-License-Identifier: Apache-2.0 | ||
| https://www.apache.org/licenses/LICENSE-2.0 --> | ||
|
|
||
| # Apache JMeter — project manifest |
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.
What
Adopts the Apache Magpie framework of
agent skills into JMeter, plus the JMeter-specific configuration, so
maintainers can run structured, auditable workflows (PR triage, issue
triage, stats dashboards, security-issue and release helpers) from their
own AI coding agent.
Committed footprint (the important part)
21 files. The split:
project.md, thepr-management-*config,.gitignore, a shortREADME/AGENTSsection,
.claude/settings.json, two relay symlinks,.apache-magpie.lock.magpie-setupbootstrap skill (~4.7k lines ofMarkdown docs, not code) — required so a fresh clone can re-fetch the
framework.
snapshot (
.apache-magpie/), fetched on demand. They never land ingit and never sit in the agent's context window (skills load on demand;
only a one-line description per skill is indexed).
Full removal is a single command:
/magpie-setup unadopt.What's wired for JMeter
pr-management,issue,security.release-*is intentionally not wired yet.
area:*labels (area groupingdisabled), no GitHub security tracker / Projects board (those panels are
N/A), real CI-check names mapped (
Validation,Error Prone, the JDK ×vendor × OS test matrix), longer grace windows for our slow triage
cadence.
dev@/private@via the ASF PonyMailarchive, ASF Vulnogram CVE tooling.
How it stays low-risk
before any comment, label, merge, or commit. No bots posting on their
own, no CI automation.
their own credentials. No shared service; no project data leaves the
maintainer's control.
PreToolUsehook blockspremature "ready", maintainer pings, and
Co-Authored-Bytrailers.Example output (read-only, nothing posted)
PR-backlog dashboard generated from our 70 open PRs by the
pr-management-statsskill:https://gistpreview.github.io/?b22eb23da618ff3b17a4e4e921375d72
Commits
magpie-setup)🤖 Generated with Claude Code