kubesphere-devops-jenkinslisted

# KubeSphere DevOps Jenkins Configuration ## Overview KubeSphere DevOps embeds Jenkins as the CI engine. Jenkins is configured via Configuration as Code (CasC) and provides the underlying pipeline execution environment. Understanding Jenkins configuration is essential for customizing agents, authentication, and resource management. ## When to Use - Accessing Jenkins console directly - Configuring LDAP or OIDC authentication - Customizing Jenkins agent images - Configuring GitLab or other SCM servers - Troubleshooting Jenkins startup issues - Updating Jenkins after DevOps upgrade - Triggering builds via API - Downloading build artifacts - Viewing build logs and status ## Accessing Jenkins Console ### Get Admin Credentials ```bash # Get Jenkins admin user and password kubectl -n kubesphere-devops-system get secret devops-jenkins -o yaml # Decode values echo "<jenkins-admin-password-base64>" | base64 -d echo "<jenkins-admin-user-base64>" | base64 -d ``` ### Get Jenkins NodePort ```bash kubectl -n kubesphere-devops-system get svc devops-jenkins # Default NodePort: 30180 ``` Access via: `http://<master-node-ip>:30180` ## Configuration As Code (CasC) Jenkins configuration is managed through the `jenkins-casc-config` ConfigMap: ```bash # View current CasC kubectl -n kubesphere-devops-system get cm jenkins-casc-config -o yaml ``` ### Key Configuration Sections ```yaml agent: jenkins: Master: NodeSelector: {} Tolerations: [] Agent: Image: "j