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

Correct Jenkins trigger safety boundary #147

New Issue
Closed
opened 2026-07-05 01:56:39 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-05 01:56:39 -05:00
Owner
Copy Link
Copy Source

Purpose

Correct Jenkins trigger safety boundary to separate read/write capabilities and enforce fail-closed mutation auditing.

Acceptance criteria

  • Move jenkins_trigger_build out of the read-only server boundary or otherwise separate read/write capability surfaces.
  • Make audit fail-closed using the established mutation audit pattern.
  • Add tests for audit failure, permission failure, bad confirmation, and successful gated trigger.
  • Update config only after operator approval of which profile, if any, may carry trigger capability.

Related to parent integrations discussion.

## Purpose Correct Jenkins trigger safety boundary to separate read/write capabilities and enforce fail-closed mutation auditing. ## Acceptance criteria * Move `jenkins_trigger_build` out of the read-only server boundary or otherwise separate read/write capability surfaces. * Make audit fail-closed using the established mutation audit pattern. * Add tests for audit failure, permission failure, bad confirmation, and successful gated trigger. * Update config only after operator approval of which profile, if any, may carry trigger capability. Related to parent integrations discussion.
jcwalker3 commented 2026-07-06 10:44:53 -05:00
Author
Owner
Copy Link
Copy Source

Closing as duplicate of #152 (canonical, absorbed via comment 4011 there). Every acceptance bullet here is subsumed by #152's fuller criteria; this issue's thread contains no unique content to preserve. Closed under duplicate-triage rules by jcwalker3 / prgs-author (gitea.issue.close capability resolved allowed).

Closing as duplicate of #152 (canonical, absorbed via comment 4011 there). Every acceptance bullet here is subsumed by #152's fuller criteria; this issue's thread contains no unique content to preserve. Closed under duplicate-triage rules by `jcwalker3 / prgs-author` (`gitea.issue.close` capability resolved allowed).
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
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#147