Hi all,
I am accepted to Google Summer of Code 2019 under Jenkins and my project is based on adding Multibranch Pipeline Support to GitLab.
Generally the SCM plugins are divided into 3 separate plugins, namely:
-
SCM-api-plugin: For wrapping API into a plugin
-
SCM-plugin: For build triggers, auth and webhooks management
-
SCM-branch-source-plugin: For branches, MRs, tags indexing and build for all jobs
e.g. - github-api-plugin, github-plugin, github-branch-source-plugin
Since, GitLab does not have such an api-plugin we decided to choose an appropriate Java API for GitLab and wrap it into a plugin. GitLab API Plugin has been released to Jenkins Plugins Centre: https://plugins.jenkins.io/gitlab-api
Find GitLab API Repository here: https://github.com/jenkinsci/gitlab-api-plugin
The reasons for choosing a gitlab4j API is mentioned in the wiki page: https://wiki.jenkins.io/display/JENKINS/GitLab+API+Plugin
Our project plan is to modify the gitlab-plugin to depend on this new api-plugin and also to develop the gitlab-branch-source-plugin to support this new api-plugin.
For more details, my proposal can be found here: https://docs.google.com/document/d/1YpuCC129U8KPXAwiXRXQ_4XWuLursPGl3rzQjz43-CY/edit?usp=sharing
Our plan right now:
-
Develop Kohsuke's GitLab Branch Source Plugin - https://github.com/jenkinsci/gitlab-branch-source-plugin.
-
Take inspiration from your codebase and give you credits
-
Collaborate with contributors of this repository for code contributions, code reviews, insights etc.
What do you think about this idea? We can work together to get it released to Jenkins Official Update Center soon.
Reporting this upon suggestion of @grfullerton jenkinsci/gitlab-plugin#499 (comment)