Plugins and Credentials

Managing Plugins

Plugins extend Jenkins: Git, GitHub, pipeline steps, Slack/email notifications, Docker, Blue Ocean UI, credentials and hundreds more. Manage them under Manage Jenkins → Plugins. Keep versions updated and remove what you do not use - every plugin adds attack surface.

Essential Plugins

• Pipeline (and Blue Ocean for a nicer UI)
• Git / GitHub integration
• Credentials Binding
• JUnit for test reports
• Docker pipeline for container builds
• SSH Agent for deploying over SSH
• Slack / Email Extension for notifications

Storing Secrets Securely

Never put passwords in the Jenkinsfile. Use Credentials → Add Credentials:

• Username with password - Git, Maven repos, APIs
• SSH key - Git over SSH, deploy hosts
• Secret text - tokens (GitHub token, Slack token, Docker registry)
• Secret file - certificates, service account JSON

Using Credentials in a Pipeline

withCredentials([string(credentialsId: 'dockerhub', variable: 'DOCKER_PASS')]) {
    sh 'echo "$DOCKER_PASS" | docker login -u you --password-stdin'
}

Key Points

• Credentials: one source of truth, injected only at build time.
• Deploy and integrate via plugins to avoid reinventing the wheel.
• Fewer, newer plugins = more secure Jenkins.