Hi Rick, I was waiting for your comment on this. My main motive was to make this decision on what I have described is whether to develop a new plugin or improvise the existing one. I'm a bit confused if we intend to take out the API from the GitLab plugin will it be able to support the existing applications. I think I need to explore a little more and come up with a clearer idea to discuss with community.
My proposal is developing in a Google doc like the rest of the community. Working on for some changes then I will be drop it in the GSoC mailing list. Hopefully today. Regards, Parichay (baymac) On Tue 2 Apr, 2019, 07:03 Rick <[email protected] wrote: > Hi, > > As said at the title. I think that the freestyle job is not in this scope. > > Second, we need a multi-branch API plugin, according to the project > proposal > https://docs.google.com/document/d/1Gqz4LyU5sw6I50OdAVsQSW_WPNDlvXg4Ic9NdcYj4Ts/edit#heading=h.pr5cab6hhyg > . > > Good to see your proposal here. But we have another mail list to a > discussion about GSoC. > https://groups.google.com/forum/#!forum/jenkinsci-gsoc-all-public > And I saw many proposals there from other students. > > If you can write your proposal in a Goole Doucment that would be easy to > comment and discuss. > > Best regards, > Rick > > > On Mon, Apr 1, 2019 at 11:58 PM Parichay Barpanda < > [email protected]> wrote: > >> Hi Matt, >> >> Yeah I lately realised freestyle jobs are important as of now. Moreover >> in the Gitlab plugin freestyle jobs will be of a concern as much as support >> of pipeline job. I think I'll explore the 2nd option more and figure out if >> the API can be driven out of the existing GitLab plugin without breaking >> anything. >> >> Thanks. >> >> >> On Mon 1 Apr, 2019, 21:20 Matt Sicker <[email protected] wrote: >> >>> I've been under the impression that freestyle jobs don't really intend >>> to go anywhere anytime soon. A lot of pipeline functionality is driven >>> by the same plugin code that freestyle jobs utilize. >>> >>> On Mon, Apr 1, 2019 at 1:45 AM Parichay Barpanda >>> <[email protected]> wrote: >>> > >>> > Hi all, >>> > >>> > I am preparing a proposal to add Multibranch Pipeline support to the >>> Gitlab plugin. Existing Gitlab plugin does not support Multibranch pipeline >>> builds in a way that it enables build triggers but cannot configure the >>> variables (basically multibranch pipeline support is non-existent) - the >>> API doesn't support it. But there are a lot of existing users that use the >>> GitLab plugin at the moment and I fear API changes might break binary >>> compatibility. >>> > >>> > My suggestions is to develop 2 new plugins: a Gitlab API plugin and a >>> Gitlab SCM Plugin. >>> > >>> > 1) Gitlab API plugin which, very similar to Github API plugin, wraps >>> the Gitlab Java API. >>> > >>> > 2) Gitlab SCM plugin which will be a major design overhaul version of >>> existing Gitlab Plugin to accomodate both pipeline and mulitbranch pipeline >>> jobs along with other type of job configurations. >>> > >>> > I have 2 ways to implement this: >>> > >>> > Method 1: >>> > 1) I am thinking freestyle jobs will be deprecated in the future in >>> favor of pipeline jobs. Gitlab plugin supports freestyle builds, so as long >>> as freestyle builds are favoured the existing Gitlab plugin will support it. >>> > 2) Focusing on just pipeline will ease the task of designing API and >>> handling the complexity due to which all the SCM plugins are divided into >>> two i.e. <scm> plugin and <scm>-branch-source plugin. >>> > >>> > Method 2: >>> > 1) If freestyle jobs are important and cannot be compromised then >>> modify the Gitlab plugin to add multibranch pipeline support and find a way >>> to take out Gitlab API and wrap it in a separate plugin. I haven't been >>> able to figure out how much security risks and backwards compatibility will >>> be involved in this method. Need someone with experience tell me about this. >>> > >>> > Main Objective of this proposal: Just have one SCM plugin which does >>> all type of jobs and remove users' confusion of having 2 separate SCM >>> plugins and code duplication. >>> > >>> > Need your feedbacks so that I can finalise which method to carry >>> forward and start working on this proposal. >>> > >>> > Thanks. >>> > >>> > Regards, >>> > Parichay (baymac) >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/a872ab3c-d180-4275-81ed-35418805bae2%40googlegroups.com >>> . >>> > For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> Matt Sicker >>> Senior Software Engineer, Jenkins Security, CloudBees >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ozOu5T7RpgO60fKhTkdur1HTRWQ7GEsqEqS9t-Y1EVe9Q%40mail.gmail.com >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAD0DWAPqBEkn-EVwfuS7C-1U8dT7sZCLnx6pD5C6e-V%3DCYB7Tg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAD0DWAPqBEkn-EVwfuS7C-1U8dT7sZCLnx6pD5C6e-V%3DCYB7Tg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > https://github.com/LinuxSuRen > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF7DJfHQvYas09HqR-kaF_S7hsb2SO0YCX9zugg1dcH0Q%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF7DJfHQvYas09HqR-kaF_S7hsb2SO0YCX9zugg1dcH0Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD0DWAN0yQ%3D068JcCYXP1M90sz66QyTR2g7s8gxuyax1v%3DVcvA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
