Jenkins + Memtro

Only when you ask, and only what it has been granted: trigger a build of a job (it runs whatever the job does, which may deploy or publish); stop a running build; disable a job so nothing can start it; enable a disabled job; delete a job or folder with all its builds permanently; cancel a build that is waiting in the queue; set or replace a job's description; set or replace a build's description; keep a build forever, or release it to normal log rotation; delete one build with its log and artifacts permanently; create a new job as a copy of an existing one; take an agent temporarily offline with a reason; bring a temporarily offline agent back online. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

Host, user ID and API token. Create a dedicated Jenkins user for Memtro with Overall/Read and Job/Read, since a token carries all of its user's permissions. Add Job/Build only if it may trigger builds, Job/Cancel to stop them, Job/Configure to disable, enable or describe jobs, Job/Delete to delete jobs, Run/Update and Run/Delete for builds, and Agent/Disconnect and Agent/Connect for agents.