thinkfleetai/thinkfleet-engine

jenkins

Manage Jenkins jobs, builds, and pipelines via the REST API.

First seen Mar 1, 2026

Installation

$ npx skills add thinkfleetai/thinkfleet-engine --skill jenkins

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from thinkfleetai/thinkfleet-engine · top by installs.

npx skills add thinkfleetai/thinkfleet-engine

Browse all from thinkfleetai/thinkfleet-engine

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,309 B
  • docs SUMMARY.md 75 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 4 installs

SKILL.md

Jenkins

Manage Jenkins jobs, builds, and pipelines via the REST API.

Environment Variables

  • JENKINS_URL - Jenkins server URL (e.g. https://jenkins.example.com)
  • JENKINS_USER - Jenkins username
  • JENKINS_TOKEN - API token (generate from user profile > Configure > API Token)

List jobs

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/api/json?tree=jobs[name,color,url]" | jq '.jobs[] | {name, color, url}'

Get job info

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/job/my-pipeline/api/json?tree=name,color,lastBuild[number,result,timestamp]" | jq .

Trigger build

curl -s -X POST -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/job/my-pipeline/build"
echo "Build triggered"

Trigger build with parameters

curl -s -X POST -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/job/my-pipeline/buildWithParameters" \
  --data-urlencode "BRANCH=main" \
  --data-urlencode "ENV=staging"
echo "Parameterized build triggered"

Get build status

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/job/my-pipeline/lastBuild/api/json?tree=number,result,duration,timestamp,building" | jq .

Get build console output

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/job/my-pipeline/lastBuild/consoleText" | tail -50

List build queue

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/queue/api/json?tree=items[task[name],why,inQueueSince]" | jq '.items[] | {job: .task.name, why, since: .inQueueSince}'

Get pipeline stages (Blue Ocean)

curl -s -u "$JENKINS_USER:$JENKINS_TOKEN" \
  "$JENKINS_URL/blue/rest/organizations/jenkins/pipelines/my-pipeline/runs/1/nodes/" | jq '.[] | {displayName, result, durationInMillis}'

Notes

  • Jenkins uses crumb-based CSRF protection; if enabled, fetch crumb first.
  • Use buildWithParameters for parameterized jobs, build for simple jobs.
  • API token is preferred over password for authentication.
  • Always confirm before triggering builds.