jenkins-rest-ops

Overview

This skill lets an agent perform Jenkins CI/CD operations by calling the Remote Access REST API directly with curl — no SDK, no pip dependency. Jenkins is path-addressed: append api/json to almost any object's URL to read it, POST to action paths to write. The agent consumes the credentials the caller injected, finds a CORE path in a bundled index, constructs the curl, and parses the JSON. It covers the feasible CORE surface — trigger/poll/status/console/list plus job CRUD and build management — and deliberately stays inside the Jenkins API (it does not commit a Jenkinsfile to a repo or configure SCM webhooks; those are vcs operations). Jenkins ships no official OpenAPI, so the CORE paths are grounded on the official Remote Access docs.

When to activate

• ✅ Triggering a build (build / buildWithParameters) and following it to a result.
• ✅ Reading build status (result / building / duration) or the console log.
• ✅ Listing / inspecting jobs, queue, nodes, views.
• ✅ Job CRUD via the Jenkins API — create (createItem + config.xml), copy, delete, enable/disable — and build management (stop/delete a build).

Do NOT activate when:

• You need to commit a Jenkinsfile / pipeline config into a repo, or configure an SCM webhook that points a repo at Jenkins — those are vcs operations (a GitHub/GitLab/Bitbucket ops skill), not Jenkins-API operations. (Creating a Jenkins job via createItem is in scope; committing pipeline source to the repo is not.)
• You only need credential setup — credentials are provided by the caller; this skill does not provision or resolve them (see references/credentials.md).
• The operation depends on a plugin-contributed endpoint — the CORE API is plugin-independent; plugin endpoints vary per install and are out of the guaranteed surface.