waiting-for-build

Waiting-for-Build Skill

What this does

1. Queries Jira board 11806 (Migrations & Networking Frontend) — active sprint, MTV quickfilter, "Waiting on build" column (statuses: MODIFIED, Dev Complete).
2. Finds each ticket's merge commit in the local git repo (searches git log --all for the ticket key).
3. Checks whether each commit is an ancestor of the latest build tip hashes (fetched automatically from the #mtv-builds Slack channel via fetch-build.py).
4. Transitions all in_build: true tickets to ON_QA in Jira (transition ID 41).
5. Renders an interactive canvas (waiting-for-build.canvas.tsx) via the canvas skill.

Default behaviour: transition is always performed. If the user explicitly says "just check" or "don't transition", skip step 4.

Step 0 — Get build tip hashes automatically from Slack

Run fetch-build.py to pull the latest build's commits from the #mtv-builds channel (from the repository root):

python3 .cursor/skills/waiting-for-build/scripts/fetch-build.py

Output example:

{
  "build_label": "IIB 2.12.0-44 | 02.06.2026 19:04 UTC",
  "build_version": "2.12.0",
  "console_plugin_commits": ["8e059c6", "cfc05ae"],
  "mtv_console_plugin_container": "8e059c6f48a7715179038e9bd12151c88c5f9bf1"
}

Pass build_version as --build-version and console_plugin_commits as positional arguments to query.py (Step 1). If console_plugin_commits is empty, fall back to the first 7 chars of mtv_console_plugin_container as the build tip.

How it works: Uses slackdump to archive channel C09DS44AQ65 (#mtv-builds), then queries the SQLite database for the latest IIB build thread.

Credentials are stored in .mcp.json → mcpServers.slack.env:

• SLACK_TOKEN — xoxc-... (Red Hat workspace, from Slack desktop app localStorage)
• SLACK_COOKIE — xoxd-... (d= cookie from Slack desktop app)
• SLACK_CHANNEL_ID — C09DS44AQ65 (#mtv-builds)
• SLACKDUMP_WORKSPACE — redhat

If fetch-build.py returns an error or empty commits, the Slack session token has expired (they rotate every few hours). Follow this recovery procedure: