Skip to content

Release 9.1.0

Choose a tag to compare

@maksimsarychau maksimsarychau released this 29 Jun 16:49

v9.1.0 — Launch Mutations (Rerun Failures + Build Now)

Advanced Zebrunner MCP Server release. Adds safe launch mutation tools, two workflow prompts for regression reruns and feature-scoped builds, and project-specific automation rules in zebrunner-config.json.


Highlights (v9.1.0)

Added — Tools

Tool Description
adv_rerun_launch_failures Rerun failed/aborted tests for one or many launches (single or batch mode). Preview/confirm with confirmation token. Requires IAM reporting:test-runs:rerun.
adv_start_launch Trigger Jenkins Build Now via Reporting API job/parameters + job:build. Resolves template launches by ID, name query, or suite_path. Preview/confirm before triggering CI. Jenkins integration only — does not work with Launch Launchers.
adv_get_launch_details New optional includeJobParameters — returns Jenkins job parameters from a prior launch for Build Now discovery.

Added — MCP Prompts (17 total, +2)

Prompt What it does
/relaunch-regression-failures Discover failed launches by milestone/build or rolling last 7 days; exclude launches matching relaunchFailures.excludeLaunchNamePatterns; orchestrate batch reruns via adv_rerun_launch_failures with preview/confirm.
/feature-scoped-launch Feature keyword → test discovery → test_run_rules TAGS per root suite → Build Now preview/confirm per suite. Jenkins suite_path resolved from args, recent launches, or user input (no static config).

Added — Instance configuration (zebrunner-config.json)

Block Purpose
localeTestRunRules When enabled and project is in projectKeys, non-en_US Build Now previews warn and auto-merge NOT_TAGS exclusions for suites listed in enUsOnlyFeatureSuites.
relaunchFailures Launch name exclusions (excludeLaunchNamePatterns, default ["Performance"]) and per-platform cap (maxLaunchesPerPlatform, default 50) for /relaunch-regression-failures.

Override via ZEBRUNNER_CONFIG_JSON env var or a custom config file path — see README.

Changed


Non-breaking / compatibility

  • All existing tools, resources, and prompts unchanged.
  • Legacy tool aliases (rerun_launch_failures, start_launch, etc.) still registered when ZEBRUNNER_REGISTER_LEGACY_ALIASES=true (default off since 9.0.0).
  • localeTestRunRules and relaunchFailures are optional — missing keys fall back to defaults; non-MFP deployments can disable locale rules and customize exclusion patterns.

Requirements & limitations

Topic Detail
Build Now Requires Zebrunner Jenkins integration. Launch Launchers are not supported by adv_start_launch.
Rerun failures Requires IAM permission reporting:test-runs:rerun on the API token.
Preview/confirm Both mutation tools require preview (dry_run / no confirm) before execution — agents must not auto-confirm.
Performance launches /relaunch-regression-failures excludes launches whose names match relaunchFailures.excludeLaunchNamePatterns (default: "Performance").

Quick start examples

Relaunch regression failures (milestone):

/relaunch-regression-failures
  projects: android,ios
  milestone: 26.19.0

Feature-scoped Build Now:

/feature-scoped-launch
  project: android
  feature: Water
  suite_name: Minimal Acceptance
  build: 50977

Direct tool (after preview):

Rerun failures for launch 132522 in project MFPAND

Upgrade checklist (9.0.5 → 9.1.0)

docker pull msarychau/mcp-zebrunner:9.1.0
# or rebuild :latest from this tag
  1. Review zebrunner-config.json — add or adjust localeTestRunRules / relaunchFailures for your projects.
  2. Confirm Zebrunner projects use Jenkins Build Now if you plan to use adv_start_launch or /feature-scoped-launch.
  3. Verify API tokens have reporting:test-runs:rerun if using rerun tools.
  4. Reconnect MCP clients (no OAuth changes in this release).

Cursor (mcp.json):

"zbr-cloud": { "url": "https://your-host/mcp" }

Claude Desktop (mcp-remote):

"zebrunner": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://your-host/mcp"]
}

Documentation


Compare: v9.0.5...v9.1.0