What problem does it solve? Driving a Jenkins server programmatically usually means pulling in an SDK or CLI, and the most common failure — treating an async build trigger as if it returned a build — produces wrong results. This Skill lets an agent perform Jenkins CI/CD operations directly against the Remote Access REST API with curl, handling the queue-item polling flow, token auth, and CSRF crumb fallback correctly. ## Core Features & Use Cases - Async build lifecycle: Trigger builds via build/buildWithParameters, poll the queue item to the executable build, then read status and console logs. - Job and build management: List and inspect jobs, views, queue, and nodes; create, copy, delete, enable, and disable jobs via config.xml; stop or delete builds. - Grounded endpoint index: An authoritative CORE path table built from official Jenkins docs, with the unofficial swaggy-jenkins OpenAPI bundled only as a schema cross-check. - Use Case: Ask the agent to trigger a parameterized build of a job, wait for it to finish, and report the result plus the console log — it triggers, polls the queue item, reads the final status, and fetches the log without ever exposing the API token. ## Quick Start Use jenkins-rest-ops to trigger a build of my deploy job with BRANCH=main, wait for it to finish, and show me the result and console log.
