jenkins

Trigger Jenkins builds, query status, and retrieve console logs via REST APIs.

7|4|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/koderover/devops-skills --skill jenkins-koderover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jenkins
Source: https://github.com/koderover/devops-skills/tree/main/jenkins
Command: npx skills add https://github.com/koderover/devops-skills --skill jenkins-koderover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious manual work of managing Jenkins CI/CD pipelines, saving DevOps and development teams time spent on repetitive build, status check, and log retrieval tasks.

Core Features & Use Cases

  • Build Triggering: Supports both standard and parameterized Jenkins job builds for deployment, testing and other CI/CD scenarios.
  • Status & Log Querying: Quickly check job status, build history, and console logs to troubleshoot build failures without logging into the Jenkins UI.
  • Job Lifecycle Management: Perform operations like stopping running builds, enabling or disabling jobs to manage pipeline resources.
  • Use Case: For a team deploying to production, use this skill to trigger a parameterized deployment build, wait for it to complete, and pull failure logs immediately if the build fails to speed up issue resolution.

Quick Start

Use the jenkins skill to trigger a parameterized build for the "deploy-prod" job with version 1.0.0 and environment prod, wait for the build to finish, and return the final build result.

Frequently Asked Questions about jenkins

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger a parameterized Jenkins build without using the UI?

Triggering a parameterized Jenkins build is handled by passing build parameters via REST API requests for CI/CD deployment scenarios. This supports both standard and parameterized jobs for rapid pipeline management.

How do I retrieve Jenkins console logs to troubleshoot a build failure?

Retrieving Jenkins console logs is done by querying build history and parsing log data through REST API interactions. This quickly provides failure logs for troubleshooting without needing to access the Jenkins UI.

Can I stop running Jenkins builds and disable jobs programmatically?

Stopping running Jenkins builds and disabling jobs is supported via job lifecycle management operations. This allows you to manage pipeline resources by enabling, disabling, or stopping active builds programmatically.

What is the best way to automate batch Jenkins job execution for production deployments?

Automating batch Jenkins job execution is best achieved by interacting with Jenkins REST APIs to handle build parameters and trigger jobs. This satisfies functional requirements for production deployment builds and rapid CI/CD pipeline management.

Does this approach work for querying Jenkins job status across multiple pipelines?

Querying Jenkins job status is supported across multiple pipelines through rapid CI/CD pipeline management interactions. This applies to DevOps scenarios requiring quick status checks and build history parsing without manual UI access.