kubesphere / kubesphere/ks-devops
Another copy of Jenkins CasC "jenkins_user.yaml" will hinder the upgrade of "jenkins.yaml"
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
If we make some upgrades into jenkins.yaml, like bumping builders' image version, people who have already installed KubeSphere 3.2.0 won't obtain those upgrades after KubeSphere upgrade. Because the jenkins_user.yaml has been fixed after the first installation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating jenkins.yaml and jenkins_user.yaml and tracing how each is installed during initial setup and upgrades. Reproduce an upgrade after changing the builder image version, then verify that upgrades from KubeSphere 3.2.0 receive the updated configuration without losing user changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, yaml
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100