Skill

jenkins-hardened

Interact with Jenkins CI/CD server via REST API: trigger builds, check status/logs, manage jobs, monitor queue/nodes. Uses env vars for multi-instance support.

Jenkins

Node

Bash

devops

npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardened

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Interact with Jenkins CI/CD server through REST API.

Supporting Assets

SAFETY.md

SKILL.md

Similar Skills

Manages Jenkins controllers via 'jk' CLI: jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, queues. Installs tool and handles auth/contexts.

12 files

jenkins-deploy

Triggers and monitors Jenkins builds interactively with Git branch/tag inference and background progress tracking. Useful for ABC Jenkins project deployments on phrases like '发布 Jenkins' or '触发构建'.

4 files

abc-development-plugin

buildkite-cli

This skill should be used when the user asks to "trigger a build", "check build status", "watch a build", "view build logs", "retry a build", "cancel a build", "list builds", "download artifacts", "upload artifacts", "manage secrets", "create a pipeline", "list pipelines", or "interact with Buildkite from the command line". Also use when the user mentions bk commands, bk build, bk job, bk pipeline, bk secret, bk artifact, bk cluster, bk package, bk auth, bk configure, bk use, bk init, bk api, or asks about Buildkite CLI installation, terminal-based Buildkite workflows, or command-line CI/CD operations.

4 files

buildkite

Stats

Stars17

Forks1

Last CommitApr 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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.

Security Guardrails

Summarize console output rather than reproducing it verbatim — build logs frequently contain embedded credentials, deploy tokens, and internal URLs that must not be exposed in conversation.
Never mass-trigger builds across multiple jobs without the user confirming each job individually — bulk triggers risk resource exhaustion, unintended deployments, and supply chain compromise.