Use when configuring Jenkins in KubeSphere DevOps, including agent customization, LDAP/OIDC integration, build artifact retrieval, or troubleshooting Jenkins issues
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…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/kubesphere-devops-jenkins · pinned to the source commit
git clone https://github.com/kubesphere/kubesphere.git
cd kubesphere
git checkout 04a29b5c601470fa6bc2f2e92358dcb802a0d414
mkdir -p ".claude/skills/kubesphere-devops-jenkins"
cp -r "skills/kubesphere-devops-jenkins" ".claude/skills/kubesphere-devops-jenkins"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 04a29b5c6014. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint 5e884898da280471
Instructs shell/process/package operations that run commands on the host.
Evidence: chmod +x· fingerprint d242f67f7a76ea57
Fetches remote content at runtime, which can change after review.
Evidence: curl· fingerprint 427e4b79b1f0fc90
Uses encoding/eval patterns that can hide executable content.
Evidence: [redacted]· fingerprint e38d194b34bd5f86