kubesphere / kubesphere/ks-devops
Make integration with GitLab be easier
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
Background
Gitlab is a hosted git service that works much like Github, with an interactive web panel for managing your projects and viewing code. More and more users choose it to host on their own sever. Some users are using KubeSphere DevOps as their CI/CD tool, but there is no interaction between DevOps and GitLab, such as sending pipeline build status back to GitLab.
Proposal
Install GitLab plugin to complete this task.
But there are two things we should pay attention to:
- Be aware of supported GitLab versions
- How to configure Jenkins-to-GitLab authentication conveniently? Or just using GitLab credential directly.
References
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 with the GitLab plugin documentation linked in the issue and inspect the repository's DevOps integration entry points. Confirm supported GitLab versions, determine how Jenkins-to-GitLab authentication should be configured, and verify that pipeline build status can be sent back to GitLab.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100