Jenkins Ops

Jenkins Operations Skill

Prerequisite: jenkins_ops.py must be available in the project's scripts/ directory or installed from this skill's scripts/ folder.

Architecture

┌─────────────────────┐      ssh user@localhost       ┌──────────────────┐
│  Jenkins (Docker)   │ ─────────────────────────▶   │   Host Machine    │
│  Scheduler only     │   all commands run here →    │  python/rsync/ssh │
│  --network host     │                              │  conda env, tools │
└─────────────────────┘                              └──────────────────┘

Core Principle: Jenkins runs in Docker as scheduler only. All tasks execute via ssh user@localhost on the host machine. Never install python/rsync inside the container.

• Default URL: http://localhost:8080
• Credentials: Set via JENKINS_URL, JENKINS_USER, JENKINS_PASS env vars
• Container: docker ps --filter name=jenkins
• Unified Interface: jenkins_ops.py (CLI + Library)

Setup

1. Copy the script to your project

cp /path/to/agent-skills/jenkins-ops/scripts/jenkins_ops.py your_project/scripts/

Or symlink:

ln -sf /path/to/agent-skills/jenkins-ops/scripts/jenkins_ops.py your_project/scripts/jenkins_ops.py

2. Environment variables (optional, defaults shown)

export JENKINS_URL="http://localhost:8080"
export JENKINS_USER="admin"
export JENKINS_PASS="admin123"

CLI Quick Reference

# List all jobs
python3 scripts/jenkins_ops.py list

# Trigger build (async, returns immediately)
python3 scripts/jenkins_ops.py fire <job-name> [PARAM=VALUE ...]

# Trigger build (sync, streams console output)
python3 scripts/jenkins_ops.py trigger <job-name> [PARAM=VALUE ...]

# Check build status
python3 scripts/jenkins_ops.py status <job-name> [build-number]

# Get console log
python3 scripts/jenkins_ops.py log <job-name> [build-number]

# Create pipeline job from Jenkinsfile
python3 scripts/jenkins_ops.py create <job-path> --script <Jenkinsfile>

# Create folder
python3 scripts/jenkins_ops.py create-folder <name> [--parent <path>]

# Update job config
python3 scripts/jenkins_ops.py update <job-path> --script <Jenkinsfile>

# Delete job
python3 scripts/jenkins_ops.py delete <job-path>

# Cancel queued build
python3 scripts/jenkins_ops.py cancel <queue-id>

# Reload configuration
python3 scripts/jenkins_ops.py reload

Library Mode (for Python scripts / MCP)

from jenkins_ops import JenkinsOps
ops = JenkinsOps()

# Health check
ops.is_available()

# Trigger + wait
result = ops.trigger("sdk-release", params={"DEPLOY_CK": "true"})
print(result["success"], result["build_number"])

# Async trigger
result = ops.fire("market-data-sync", params={"START_DATE": "20260210"})
print(result["queue_id"])

# Job lifecycle
ops.create_folder("my_folder")
ops.create_pipeline("my_folder/build", script_path="/path/to/Jenkinsfile")
ops.update_config("my_folder/build", script_path="/new/Jenkinsfile")
ops.delete_job("my_folder/build")

# Auto-provision project jobs
ops.ensure_project_jobs("devloop", "my_project", {
    "build": "/path/to/Jenkinsfile.build",
    "run": "/path/to/Jenkinsfile.run",
})

Pipeline Pattern

All pipelines should use the SSH-to-host pattern:

pipeline {
    agent any
    environment {
        SSH = 'ssh -o StrictHostKeyChecking=no -o BatchMode=yes user@localhost'
    }
    stages {
        stage('Example') {
            steps {
                sh "${SSH} bash /path/to/your/script.sh"
            }
        }
    }
}

⚠️ Key Notes:

• Non-interactive SSH doesn't load .bashrc — use full python paths
• Use host absolute paths, not /workspace/...
• Commands with complex quoting must be wrapped in script files
• No \ line continuations in Groovy sh strings (XML compression breaks them)

Anti-Patterns

❌ Installing python/rsync/tools inside the Jenkins container
   → All tools live on the host machine. Container = scheduler only

❌ Using container paths (/workspace/...) in pipeline scripts
   → Use host absolute paths (/home/user/...)

❌ Using \ line continuation in Groovy sh strings
   → XML compression breaks them. Use single-line commands or external script files

❌ Running commands directly in Jenkins container instead of SSH-to-host
   → ALL task execution goes through: ssh user@localhost 'command'

❌ Bypassing jenkins_ops.py to call Jenkins REST API directly
   → jenkins_ops.py handles CRUMB, auth, XML config. Direct API calls will miss these

❌ Using interactive SSH in pipelines
   → Use -o BatchMode=yes -o StrictHostKeyChecking=no for non-interactive SSH

Troubleshooting

Rules

1. Jenkins = Scheduler Only: All commands execute on host via SSH
2. jenkins_ops.py only: All Jenkins operations go through the unified script
3. Absolute paths: Scripts use host absolute paths, not container paths
4. Audit trail: Use Jenkins for all periodic/CI tasks to maintain audit history