Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Jenkins Pipeline

  • 1.1k installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

jenkins-pipeline is a prompt skill for Jenkins declarative pipeline Jenkinsfile authoring.

About

The jenkins-pipeline skill provides prompt templates and patterns for authoring Jenkins declarative pipelines with checkout, build, test, artifact archive, and deployment stages. It documents agent labels, environment blocks, parallel stages, credentials binding, and post actions for success or failure notifications. Agents scaffold Jenkinsfiles aligned with common stack patterns while keeping secrets in Jenkins credential stores instead of plaintext. The skill helps teams modernize freestyle jobs into pipeline-as-code with reproducible stage boundaries and clear failure diagnostics.

  • Declarative Jenkins pipeline Jenkinsfile patterns.
  • Checkout, build, test, archive, and deploy stages.
  • Parallel stages, credentials binding, and post actions.
  • Secrets via Jenkins credential stores, not plaintext.
  • Pipeline-as-code migration from freestyle jobs.

Jenkins Pipeline by the numbers

  • 1,100 all-time installs (skills.sh)
  • +28 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #173 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
From the docs

What jenkins-pipeline says it does

Jenkins pipeline
SKILL.md
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill jenkins-pipeline

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.1k
repo stars305
Security audit3 / 3 scanners passed
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How should I structure this Jenkins pipeline for build, test, and deploy?

Author Jenkins declarative pipeline Jenkinsfiles for build, test, and deploy stages.

Who is it for?

Teams writing or migrating Jenkins pipeline-as-code jobs.

Skip if: Skip for GitHub Actions or GitLab CI when Jenkins is not the target.

When should I use this skill?

User authors or refactors Jenkins declarative pipelines and Jenkinsfiles.

What you get

Declarative Jenkinsfile with staged workflow and credential-safe configuration.

  • Jenkinsfile
  • declarative pipeline stages
  • parameterized deploy configuration

Files

SKILL.mdMarkdownGitHub ↗

Jenkins Pipeline

Table of Contents

Overview

Create enterprise-grade Jenkins pipelines using declarative and scripted approaches to automate building, testing, and deploying with advanced control flow.

When to Use

  • Enterprise CI/CD infrastructure
  • Complex multi-stage builds
  • On-premise deployment automation
  • Parameterized builds

Quick Start

Minimal working example:

pipeline {
    agent { label 'linux-docker' }
    environment {
        REGISTRY = 'docker.io'
        IMAGE_NAME = 'myapp'
    }
    parameters {
        string(name: 'DEPLOY_ENV', defaultValue: 'staging')
    }
    stages {
        stage('Checkout') { steps { checkout scm } }
        stage('Install') { steps { sh 'npm ci' } }
        stage('Lint') { steps { sh 'npm run lint' } }
        stage('Test') {
            steps {
                sh 'npm run test:coverage'
                junit 'test-results.xml'
            }
        }
        stage('Build') {
            steps {
                sh 'npm run build'
                archiveArtifacts artifacts: 'dist/**/*'
            }
        }
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Declarative Pipeline (Jenkinsfile)Declarative Pipeline (Jenkinsfile)
Scripted PipelineScripted Pipeline (Groovy), Multi-Branch Pipeline, Parameterized Pipeline, Pipeline with Credentials

Best Practices

✅ DO

  • Use declarative pipelines for clarity
  • Use credentials plugin for secrets
  • Archive artifacts and reports
  • Implement approval gates for production
  • Keep pipelines modular and reusable

❌ DON'T

  • Store credentials in pipeline code
  • Ignore pipeline errors
  • Skip test coverage reporting
  • Use deprecated plugins

Related skills

FAQ

Which pipeline syntax?

Jenkins declarative pipeline Jenkinsfile patterns.

How are secrets handled?

Bind Jenkins credentials stores; avoid plaintext secrets in Jenkinsfiles.

What stages are typical?

Checkout, build, test, artifact archive, and deployment with post actions.

Is Jenkins Pipeline safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.