Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 78 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

MCP Control Plane umbrella: Jenkins + GlitchTip integrations #75

New Issue
Closed
opened 2026-07-02 05:46:25 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-02 05:46:25 -05:00
Owner
Copy Link
Copy Source

Curated 2026-07-02 to reflect review consensus (issue text only; not started).

Umbrella / tracking issue only. No implementation acceptance criteria live
here — they belong to the child issues.

Children

  • #71 — ADR: confirm + extend trust-boundary model (Jenkins/GlitchTip).
  • #76 — Multi-service profile/config schema (library, not shared creds).
  • #72 — Jenkins read-only build-status tools design. #77 — Jenkins job mapping.
  • #73 — GlitchTip read-only issue/event tools design.
  • #74 — GlitchTip->Gitea filing workflow (orchestrated). #78 — dedup/linking.
  • #79 — Apply ADR decisions to boundary/safety docs.
  • #80 — Label proposal (approval-gated).

Sequencing

ADR (#71) + profile schema (#76) -> read-only designs (#72/#73, #77) ->
orchestrated filing (#74/#78) -> doc application (#79) / labels (#80).

Phase 1 non-goals (hard)

  • No Jenkins build triggers.
  • No deploys.
  • No auto-filing of GlitchTip issues.
  • No single MCP server holding Gitea + Jenkins + GlitchTip credentials.
  • Implementation work waits on the ADR / boundary decisions (#71).
_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ **Umbrella / tracking issue only.** No implementation acceptance criteria live here — they belong to the child issues. ## Children * #71 — ADR: confirm + extend trust-boundary model (Jenkins/GlitchTip). * #76 — Multi-service profile/config schema (library, not shared creds). * #72 — Jenkins read-only build-status tools design. #77 — Jenkins job mapping. * #73 — GlitchTip read-only issue/event tools design. * #74 — GlitchTip->Gitea filing workflow (orchestrated). #78 — dedup/linking. * #79 — Apply ADR decisions to boundary/safety docs. * #80 — Label proposal (approval-gated). ## Sequencing ADR (#71) + profile schema (#76) -> read-only designs (#72/#73, #77) -> orchestrated filing (#74/#78) -> doc application (#79) / labels (#80). ## Phase 1 non-goals (hard) * **No Jenkins build triggers.** * **No deploys.** * **No auto-filing of GlitchTip issues.** * **No single MCP server holding Gitea + Jenkins + GlitchTip credentials.** * Implementation work **waits on the ADR / boundary decisions (#71)**.
jcwalker3 added the mcpsecurityroadmapjenkinsglitchtip labels 2026-07-02 05:46:48 -05:00
jcwalker3 commented 2026-07-02 16:01:42 -05:00
Author
Owner
Copy Link
Copy Source

Umbrella closure — phase-1 design complete

All nine tracked children are closed, each landed via a merged PR:

Child Scope Landed via
#71 ADR: trust-boundary model confirmed + extended decisions recorded on tracker; applied via #79
#76 Multi-service profile/config schema PR #92
#72 Jenkins read-only build-status tools design PR #88
#77 Jenkins repo/branch/PR -> job mapping design PR #91
#73 GlitchTip read-only error/event tools design PR #93
#74 GlitchTip->Gitea filing workflow design PR #94
#78 GlitchTip/Gitea dedup + linking design PR #95
#79 ADR decisions applied to boundary/safety docs PR #89
#80 Label taxonomy proposal (approval-gated) PR #90

Phase-1 non-goals were honored throughout: no Jenkins build triggers, no deploys, no auto-filing, no shared-credential server — no Jenkins/GlitchTip implementation code exists in this repo.

Phase 2 (implementation) is intentionally NOT tracked here. Per ADR-0001's repo-shape direction, implementation belongs in the mcp-control-plane packages (jenkins-mcp, glitchtip-mcp, orchestrator) once the owner settles the repo-location decision. When that starts, open fresh implementation issues in the appropriate tracker rather than reviving this design umbrella.

Closing as completed.

## Umbrella closure — phase-1 design complete All nine tracked children are closed, each landed via a merged PR: | Child | Scope | Landed via | |---|---|---| | #71 | ADR: trust-boundary model confirmed + extended | decisions recorded on tracker; applied via #79 | | #76 | Multi-service profile/config schema | PR #92 | | #72 | Jenkins read-only build-status tools design | PR #88 | | #77 | Jenkins repo/branch/PR -> job mapping design | PR #91 | | #73 | GlitchTip read-only error/event tools design | PR #93 | | #74 | GlitchTip->Gitea filing workflow design | PR #94 | | #78 | GlitchTip/Gitea dedup + linking design | PR #95 | | #79 | ADR decisions applied to boundary/safety docs | PR #89 | | #80 | Label taxonomy proposal (approval-gated) | PR #90 | Phase-1 non-goals were honored throughout: no Jenkins build triggers, no deploys, no auto-filing, no shared-credential server — no Jenkins/GlitchTip implementation code exists in this repo. **Phase 2 (implementation) is intentionally NOT tracked here.** Per ADR-0001's repo-shape direction, implementation belongs in the `mcp-control-plane` packages (`jenkins-mcp`, `glitchtip-mcp`, orchestrator) once the owner settles the repo-location decision. When that starts, open fresh implementation issues in the appropriate tracker rather than reviving this design umbrella. Closing as completed.
jcwalker3 commented 2026-07-05 01:56:50 -05:00
Author
Owner
Copy Link
Copy Source

Jenkins & GlitchTip MCP Integration Child Issues Created

Following the operator decision on the Jenkins and GlitchTip MCP status audit, five child implementation issues have been created to track the remaining gaps:

  1. #146: Fix MCP registration and naming for Jenkins/GlitchTip servers
  2. #147: Correct Jenkins trigger safety boundary
  3. #148: Complete GlitchTip-to-Gitea filing orchestrator
  4. #149: Update operator runbooks and roadmap docs
  5. #150: Add integration/discoverability coverage

These issues will track the necessary work to align the safety boundaries, audits, naming conventions, and docs for the Jenkins and GlitchTip integrations.

## Jenkins & GlitchTip MCP Integration Child Issues Created Following the operator decision on the Jenkins and GlitchTip MCP status audit, five child implementation issues have been created to track the remaining gaps: 1. **#146**: Fix MCP registration and naming for Jenkins/GlitchTip servers 2. **#147**: Correct Jenkins trigger safety boundary 3. **#148**: Complete GlitchTip-to-Gitea filing orchestrator 4. **#149**: Update operator runbooks and roadmap docs 5. **#150**: Add integration/discoverability coverage These issues will track the necessary work to align the safety boundaries, audits, naming conventions, and docs for the Jenkins and GlitchTip integrations.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels glitchtip jenkins mcp roadmap security
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#75