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

Investigate Jenkins read-only build status tools #72

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

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

Design the read-only Jenkins MCP tool set that answers whether a project
build succeeded or failed. Belongs in a separate jenkins-mcp trust boundary
(per #71 decision), never inside the Gitea MCP.

Acceptance criteria

  • Defines the minimum read-only tool set (e.g. list jobs, latest build, build
    status, get build, bounded console tail).
  • Covers latest build status; build URL, number, timestamp, duration, branch,
    result.
  • Build triggers explicitly excluded.
  • Deploy triggers explicitly excluded.
  • Parameterized job launches explicitly excluded.
  • Console output must be bounded and redacted.
  • Jenkins credentials never enter the Gitea MCP runtime.
  • Defines behavior for unknown jobs and when Jenkins is unavailable.
  • Produces implementation-ready design notes (no implementation here).

Parent: #75. Related: #77 (job mapping).

_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ Design the **read-only** Jenkins MCP tool set that answers whether a project build succeeded or failed. Belongs in a separate `jenkins-mcp` trust boundary (per #71 decision), never inside the Gitea MCP. ## Acceptance criteria * Defines the minimum read-only tool set (e.g. list jobs, latest build, build status, get build, bounded console tail). * Covers latest build status; build URL, number, timestamp, duration, branch, result. * **Build triggers explicitly excluded.** * **Deploy triggers explicitly excluded.** * **Parameterized job launches explicitly excluded.** * Console output must be **bounded and redacted**. * **Jenkins credentials never enter the Gitea MCP runtime.** * Defines behavior for unknown jobs and when Jenkins is unavailable. * Produces implementation-ready design notes (no implementation here). Parent: #75. Related: #77 (job mapping).
jcwalker3 added the read-onlydesignjenkins labels 2026-07-02 05:44:16 -05:00
jcwalker3 added the status:in-progress label 2026-07-02 13:32:04 -05:00
sysadmin removed the status:in-progress label 2026-07-02 14:01:37 -05:00
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 design jenkins read-only
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#72