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

Draft ADR for Jenkins, GlitchTip, and MCP Control Plane architecture #71

New Issue
Open
opened 2026-07-02 05:43:38 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:43:38 -05:00
Owner
Copy Link
Copy Source

Before adding Jenkins or GlitchTip tools, create an architecture decision record explaining whether this repo should remain Gitea-Tools or evolve into a broader MCP Control Plane.

The ADR should evaluate:

  • Keeping this repo Gitea-only.
  • Renaming/evolving into MCP Control Plane.
  • Extracting shared MCP utilities into a package.
  • Separate namespaces for:
    • gitea-*
    • jenkins-*
    • glitchtip-*
    • release-*
  • Read-only tools vs mutation tools.
  • Shared profile/config/audit model across services.
  • Credential separation per service.
  • How to prevent mcp_server.py from becoming a giant monolith.

Acceptance criteria

  • ADR file added under docs/architecture or equivalent.
  • Recommends a clear direction.
  • Defines initial boundaries for Jenkins and GlitchTip.
  • Defines read-only-first policy.
  • Defines mutation gating expectations.
  • Defines shared config/profile/audit requirements.
  • Does not implement Jenkins or GlitchTip tools.
Before adding Jenkins or GlitchTip tools, create an architecture decision record explaining whether this repo should remain `Gitea-Tools` or evolve into a broader MCP Control Plane. The ADR should evaluate: * Keeping this repo Gitea-only. * Renaming/evolving into MCP Control Plane. * Extracting shared MCP utilities into a package. * Separate namespaces for: * `gitea-*` * `jenkins-*` * `glitchtip-*` * `release-*` * Read-only tools vs mutation tools. * Shared profile/config/audit model across services. * Credential separation per service. * How to prevent `mcp_server.py` from becoming a giant monolith. ## Acceptance criteria * ADR file added under docs/architecture or equivalent. * Recommends a clear direction. * Defines initial boundaries for Jenkins and GlitchTip. * Defines read-only-first policy. * Defines mutation gating expectations. * Defines shared config/profile/audit requirements. * Does not implement Jenkins or GlitchTip tools.
jcwalker3 added the architecturedesignjenkinsglitchtip labels 2026-07-02 05:44:13 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label architecture design glitchtip jenkins
Milestone
No items
No Milestone
Projects
Clear projects
No project
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#71
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?