kubesphere / kubesphere/ks-devops
Support to communicate with Giltab directly using the original APIs instead of the Jenkins proxy mode
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
Since KubeSphere DevOps v3.3.0, we are using the original APIs of GitHub, Bitbucket, and Git. But we still need to call the Jenkins APIs to fetch information from Gitlab.
- #692
/kind feature
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 issue #692 and trace how GitLab information is currently fetched through the Jenkins proxy. Compare that path with the repository's use of original APIs for GitHub, Bitbucket, and Git, then define the entry points needed for direct GitLab communication. Done means GitLab information is retrieved through its original APIs without the Jenkins proxy mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- api, backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100