kubesphere / kubesphere/ks-devops

[Pipeline Improvement] Multi-branch pipeline & SCM pipeline

Open
#849 0 comments 0 reactions 0 assignees View on GitHub
kind/feature
Dominant language
Go
Stars
164
Forks
140
PR merge metrics
No merged PRs in 30d

Description

### What is version of KubeSphere DevOps has the issue?

v3.3.1

### How did you install the Kubernetes? Or what is the Kubernetes distribution?

kubekey

### Describe this feature

- [ ] https://github.com/kubesphere/ks-devops/issues/843
- [ ] https://github.com/kubesphere/ks-devops/issues/774

mentioned in https://kubesphere.com.cn/forum/d/9011-kubesphere-v331jenkinsfile
If need to create multi-branch pipeline, should select git repo
If need to create normal pipeline, should not select git repo
Jenkinsfile in SCM is not supported

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reading linked issues 843 and 774, then review the referenced forum discussion about the Jenkinsfile behavior. Confirm the expected distinction between multi-branch and normal pipelines and the requested SCM Jenkinsfile support; the work is done when those requirements are explicitly supported and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, kubernetes
Domain
ci-cd, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.