kubesphere-devops-pipeline
Use when creating, running, or managing CI/CD pipelines in KubeSphere DevOps, including pipeline API operations and run monitoring
npx skills add kubesphere/kubesphere --skill kubesphere-devops-pipeline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides a agent to manage KubeSphere DevOps pipelines by creating and triggering PipelineRun resources, checking their status, and handling multi-branch pipelines and credentials. It includes examples for creating PipelineRun, checking status, deleting runs, and monitoring progress, plus steps for single and multi-branch pipelines with consideration for private repositories and required creator annotations.
How it works
- Emphasizes creating a PipelineRun resource to trigger a pipeline, with metadata (name, namespace) and spec (pipelineRef, parameters).
- Shows how to apply the PipelineRun using kubectl and how to query status via kubectl get commands.
- Provides a schema for PipelineRun status fields: status.phase, status.conditions, status.completionTime, status.startTime.
- Demonstrates creating a Pipeline resource (single-branch and multi-branch) with a Jenkinsfile, including examples using agent kubernetes with a pod YAML and steps such as sh and archiveArtifacts.
- Details the requirement to include kubesphere.io/creator annotations for tenant-created resources and its impact on ownership and RBAC.
- Outlines a multi-branch pipeline workflow, including repository checks (private vs public), credential creation for private repos, and referencing credentials via git_source.credential_id.
- Describes how to trigger multi-branch pipeline runs via PipelineRun with scm.refName and scm.refType.
- Provides commands to trigger repository scans and fetch logs using v1alpha2, and how to check discovered branches.
- Includes complete private repo setup steps and examples for verifying creation and retrieving pipeline details, including API calls and jq-based extraction.
When to use it
- Creating or updating CI/CD pipelines
- Triggering pipeline runs
- Monitoring pipeline execution
- Retrieving pipeline logs and artifacts
- Troubleshooting failed pipeline runs
What it can touch
- kubectl: apply, get, delete for PipelineRun and Pipeline resources
- curl: API calls to kubeSphere DevOps endpoints for credentials and pipelines
- jq: parsing of API responses for verification
- YAML payloads for Pipeline and PipelineRun definitions
Caveats
- Requires the kubesphere.io/creator annotation for tenant-created pipelines; otherwise UI visibility and RBAC may be affected
- For multi-branch pipelines, repository type must be confirmed before proceeding to credential handling
- Private repository pipelines require creating a basic-auth credential and referencing it via credential_id
- Uses v1alpha2 API for repository scanning (not v1alpha3)
# KubeSphere DevOps Pipeline Management ## Overview Pipelines in KubeSphere DevOps are Kubernetes custom resources that integrate with Jenkins. KubeSphere uses a cloud-native, object-reconcile approach where Kubernetes resources are the source of truth. ## When to Use - Creating or updating CI/CD pipelines - Triggering pipeline runs - Monitoring pipeline execution - Retrieving pipeline logs and artifacts - Troubleshooting failed pipeline runs ## Architecture Mapping KubeSphere DevOps maps Kubernetes resources to Jenkins objects: | KubeSphere Resource | K8s Resource | Jenkins Resource | |---------------------|--------------|------------------| | DevOpsProject | DevOpsProject CR + Namespace | Folder | | Pipeline | Pipeline CR | WorkflowJob | | PipelineRun | PipelineRun CR | Build Run | | Workspace | Workspace CR | (authorization context) | ``` KubeSphere Kubernetes Jenkins ───────────────────────────────────────────────────────────── Workspace demo └── DevOpsProject → demo-project NS → Folder demo-project └── Pipeline → Pipeline CR → WorkflowJob └── Run → PipelineRun CR → Build #1 ``` ## Triggering Pipeline Runs (Recommended: Object-Reconcile) > **CRITICAL: ALWAYS Check for Parameter
- Overview
- When to Use
- Architecture Mapping
- Triggering Pipeline Runs (Recommended: Object-Reconcile)
- Create a PipelineRun
- Check PipelineRun Status
- PipelineRun Status Fields
- Delete a PipelineRun
- Working Pipeline Example
- Pipeline Resource
- Tenant-Created Resources: Creator Annotation
- Multi-Branch Pipeline
- Create Multi-Branch Pipeline
- Trigger Multi-Branch Pipeline Run
kubectl apply -f pipelinerun.yaml
List all runs
kubectl get pipelineruns -n demo-project
Get specific run status
kubectl get pipelinerun my-pipeline-run-001 -n demo-project -o yaml
Watch run progress
kubectl get pipelineruns -n demo-project -w
kubectl delete pipelinerun my-pipeline-run-001 -n demo-project
curl -s -X POST "${KUBESPHERE_API}/kapis/devops.kubesphere.io/v1alpha3/namespaces/demo-project/pipelines" \
Create GitHub credentialWhat does the kubesphere-devops-pipeline skill do?
Use when creating, running, or managing CI/CD pipelines in KubeSphere DevOps, including pipeline API operations and run monitoring
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill kubesphere-devops-pipeline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.