[TRUNK-17578] Add Atlassian Bamboo CI provider documentation for Flaky Tests#436
Closed
samgutentag wants to merge 3 commits intomainfrom
Closed
[TRUNK-17578] Add Atlassian Bamboo CI provider documentation for Flaky Tests#436samgutentag wants to merge 3 commits intomainfrom
samgutentag wants to merge 3 commits intomainfrom
Conversation
New CI provider guide with Bamboo Plan Spec examples (XML, Bazel, XCode), PR number detection workaround via TRUNK_PR_NUMBER, and integration into summary sidebar, CI providers README card grid, and shared includes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
samgutentag
force-pushed
the
sam/add-bamboo-ci-provider-docs
branch
from
ebd0af6 to
ad94df5
Compare
Replaces bamboo.md with atlassian-bamboo.md featuring: - Complete Bamboo Plan Spec YAML examples with JUnit, Bazel, and XCResult tabs - PR number detection workaround section (TRUNK_PR_NUMBER / --pr-number) - Bamboo environment variables reference table - final-tasks usage explanation for upload-on-failure - Updated card grids in README and shared include - Updated summary.md TOC entry Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
samgutentag
changed the title
7 tasks
Member
Author
|
Closing — generated by an earlier version of the docs pipeline. Will re-run with updated skill. |
5 tasks
samgutentag
added a commit
that referenced
this pull request
Mar 16, 2026
## Summary Replaces the previous agent-based approach (6 separate agent files) with a single consolidated `write-docs` skill that handles the full notes-to-PR documentation workflow. • **Skill:** `.claude/skills/write-docs/` — processes raw notes, Slack threads, and engineer context into polished docs changes with full project tracking • **Pipeline:** Parse notes → duplicate check → research (Linear + Slite + Slack + docs + code) → sources audit trail → draft docs → branch/PR/Linear → Slack post → HTML review report • **Drafts template:** `.claude/drafts/TEMPLATE.md` for standardized input format ### MCP integrations The skill uses four MCP servers during Phase 2 research: - **Slack** — searches `#team-merge-queue`, `#team-flaky-tests`, and other channels for product discussion, changelogs, and context threads - **Slite** — retrieves PRDs, specs, roadmap items, and knowledge base articles for product intent and requirements - **Linear** — fetches tickets, customer asks, and related engineering issues - **Trunk Docs (GitBook)** — searches existing published docs for gap analysis ### Code-is-law principle Planning docs (Slite specs, PRDs, Slack discussions) provide valuable context but frequently diverge from what actually ships. The skill now enforces: - **Code is the authoritative source** — PR diffs and source on `main` override planning docs when they conflict - **Sources audit requires a "Differences: Code vs. Planning Docs" table** — surfacing discrepancies before they become inaccurate docs - **Unimplemented spec features are flagged as open questions**, not documented as existing functionality This was validated by running the prometheus-metrics-endpoint draft through research, which found 6 discrepancies between the Slite spec and actual code (missing metric, different queue depth definition, unimplemented features). ### Key conventions - Branch format: `<git-username>/<kebab-case-topic>` - PR titles: `[TRUNK-XXXXX] Short descriptive title` - One draft = one branch = one PR = one Linear ticket - All staged outputs under `.claude/tmp/` (gitignored) ### Validated with 8 documentation PRs | Draft | PR | Linear | |---|---|---| | google-cloud.md | #438 | TRUNK-17580 | | atlassian-bamboo.md | #436 | TRUNK-17578 | | flaky-tests-rules-engine.md | #434 | TRUNK-17576 | | new-merge-graph-ui.md | #433 | TRUNK-17575 | | merge-queue-api-endpoints.md | #439 | TRUNK-17581 | | falky-test-cyprus.md | #435 | TRUNK-17577 | | concurrency-settings.md | #437 | TRUNK-17579 | | run-tests-private-fork.md | #445 | TRUNK-17582 | ## Test plan - [ ] Verify skill invocation via `/write-docs <draft-file>` - [ ] Confirm duplicate/overlap detection works (Phase 0) - [ ] Confirm Slack/Slite MCP research surfaces relevant context during Phase 2 - [ ] Verify sources audit file includes code-vs-planning-docs comparison - [ ] Review GitBook preview for any docs changes 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.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
1 participant
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.
Summary
flaky-tests/get-started/ci-providers/atlassian-bamboo.mdbamboo.mdwith a more complete page matching existing CI provider doc patterns--pr-numberflag /TRUNK_PR_NUMBERenv varsummary.mdTOCContext
Bamboo CI support was added in analytics-cli#1017 (merged 2026-02-03). The
--pr-number/TRUNK_PR_NUMBERworkaround was added in analytics-cli#1032 per TRUNK-17515, since Bamboo does not always expose PR numbers via env vars.Linear ticket: TRUNK-17578
Review Checklist
bamboo.pnglogo asset at.gitbook/assets/bamboo.png${bamboo.TRUNK_TOKEN}variable syntax matches actual Bamboo plan variable interpolationTest plan
Generated with Claude Code