Back to skills
extension
Category: Development & EngineeringAPI key required

Jenkins

Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkin...

personAuthor: guowayhubclawhub

Jenkins

Interact with Jenkins CI/CD server through REST API.

Required environment variables

  • JENKINS_URL (example: https://jenkins.example.com)
  • JENKINS_USER (your Jenkins username)
  • JENKINS_API_TOKEN (API token from Jenkins user settings)

List jobs

node {baseDir}/scripts/jenkins.mjs jobs
node {baseDir}/scripts/jenkins.mjs jobs --pattern "deploy-*"

Trigger build

node {baseDir}/scripts/jenkins.mjs build --job "my-job"
node {baseDir}/scripts/jenkins.mjs build --job "my-job" --params '{"BRANCH":"main","ENV":"dev"}'

Check build status

node {baseDir}/scripts/jenkins.mjs status --job "my-job"
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs status --job "my-job" --last

View console output

node {baseDir}/scripts/jenkins.mjs console --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs console --job "my-job" --last --tail 50

Stop build

node {baseDir}/scripts/jenkins.mjs stop --job "my-job" --build 123

View queue

node {baseDir}/scripts/jenkins.mjs queue

View nodes

node {baseDir}/scripts/jenkins.mjs nodes

Notes

  • URL and credentials are variables by design for cross-environment deployment.
  • API responses are output as JSON.
  • For parameterized builds, use --params with JSON string.