jenkins

Best Practices

• Use JCasC (jenkins.yaml) for all Jenkins system configuration — avoid manual UI changes
• Reference secrets via environment variables using ${VAR} syntax in JCasC — never hardcode credentials
• Define security realm and authorization strategy explicitly (LDAP, SAML, role-based)
• Configure Kubernetes or Docker cloud agents for dynamic, ephemeral build executors
• Use Job DSL seed jobs to generate all pipeline jobs from code — single source of truth
• Set buildDiscarder with logRotator on all jobs to prevent unbounded disk growth
• Use folder() to organize jobs by team, project, or environment
• Define global tool installations (JDK, Node.js, Maven) in the tool section for consistent builds
• Use multibranchPipelineJob for repositories that need per-branch pipeline execution
• Configure credentials at the system level with scoped access (GLOBAL, SYSTEM, folder-level)
• Set scmCheckoutRetryCount for resilience against transient SCM failures
• Use shared libraries defined in unclassified.globalLibraries for cross-pipeline code reuse
• Enable CSRF protection and agent-to-controller security in the security configuration
• Use orphanedItemStrategy to clean up stale branches and PRs in multibranch pipelines