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

Jenkins repo/branch/PR to job mapping design #77

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

Design how repositories, branches, and PRs map to Jenkins jobs.

Focused split from #72 (Jenkins read-only build status tools), which references job mapping as a single criterion. This issue owns the mapping design in full.

Acceptance criteria

  • Defines project/repo/branch to Jenkins job mapping format.
  • Supports foldered Jenkins jobs if needed.
  • Handles unmapped repos/branches with explicit "no mapping" response.
  • Does not guess job names silently.
  • Documents where mapping config lives.
  • Documents testing strategy with mocked Jenkins API.
  • Does not introduce Jenkins write actions.
Design how repositories, branches, and PRs map to Jenkins jobs. Focused split from #72 (Jenkins read-only build status tools), which references job mapping as a single criterion. This issue owns the mapping design in full. ## Acceptance criteria * Defines project/repo/branch to Jenkins job mapping format. * Supports foldered Jenkins jobs if needed. * Handles unmapped repos/branches with explicit "no mapping" response. * Does not guess job names silently. * Documents where mapping config lives. * Documents testing strategy with mocked Jenkins API. * Does not introduce Jenkins write actions.
jcwalker3 added the mcpread-onlydesignjenkins labels 2026-07-02 05:46:54 -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 design jenkins mcp read-only
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#77
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?