[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson updated JENKINS-57677 Student has completed this task Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Marky Jackson Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.15315.1559144220315%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Okay, we will create a new issue when about to host the plugin. Can you resolve it Marky Jackson? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.15310.1559144160108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Parichay Barpanda since you created the repo, I would say this task is completed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.15306.1559143980200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda assigned an issue to Parichay Barpanda Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda Assignee: Oleg Nenashev Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.15302.1559143860307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda Sprint: GSoC 2019. Community Bonding Coding Phase 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.14924.1559127900245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Parichay Barpanda updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Parichay Barpanda
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-pluginDetailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}} and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete complete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Parichay Barpanda updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Parichay Barpanda
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}} and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin GitLab Branch Source Plugin has been created here - [#https://github.com/baymac/gitlab-branch-source-plugin] The repository will also contain server configuration implementation and later moved into a different plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12031.1558821120277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda URL: https://github.com/baymac/gitlab-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12035.1558821120369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Parichay Barpanda Labels: gsoc-2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.12027.1558820820186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Mark Waite
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}} and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}}and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Change By:
Mark Waite
For the GSoC project [gitlab-branch-source-plugin|https://issues.jenkins-ci.org/issues/?jql=project+%3D+JENKINS+AND+component+%3D+gitlab-branch-source-plugin] the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of {{SCM API}}and {{Branch API}} Plugins to understand the classes needs to be implemented in {{GitLab Branch Source Plugin}}. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it.3) I have been studing the codebases of {{ArgelBargel's GitLab Branch Source Plugin}}, {{GitHub Branch Source Plugin}}and {{Gitea Plugin}}. My takeaway was {{GitLab BS}} has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example,i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like {{SCMSource}} has been broken down to other sub classes , {{SCMHeadCategory}} has some different implementation, {{SCMFileSystem}} is not implemented, APIs implementation also needs to be changed and the list goes on..ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new {{GitLab Branch Source Plugin}} which will be heavily inspired from {{Gitea Plugin}} (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from {{GitLab Branch Source}} and {{GitHub Branch Source}} Plugins.iii) I will send my compelete list of reasons not to develop the existing {{GitLab Branch Source}} Plugin.
Add Comment
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Rick commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin That's a good idea. We can start from design, coding. When we think it's ready. Then fork it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11944.1558797240251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin I have sent an email to the Jenkins-dev mailing list here: https://groups.google.com/forum/#!topic/jenkinsci-dev/k_12IoFRNHg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11931.1558795200184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin I don't think hosting our plugin I'm 'jenkinsci' org is an urgent requirement. Although I agree we should start this process early lest it takes time. I will start a new repo on the test org I created for GSoC (I'll add you there) and when our plugin reaches releasable state, we can always fork it into 'jenkinsci' org. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11935.1558795200276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Parichay Barpanda Oleg Nenashev I think in the interest of time we should just use the current plugin GitHub repo (https://github.com/jenkinsci/gitlab-branch-source-plugin). So we will need to request access to this by becoming the maintainers, is that correct Oleg Nenashev and to do so we will need to request that through the jenkins-dev mailing? If so, I fear that the usual time it takes for the to happen can be lengthily, is there something we can do to expedite that faster Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11925.1558794300175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Marky Jackson I got this. I have already hosted a plugin so I am aware of the procedure. In that case there was also a conflicting plugin name and the older plugin was renamed and archived. You just have to handle this initial part. i.e. discuss with Kohsuke Kawaguchi to either allow us push access to GitLab Branch Source Plugin or follow the archiving procedure. After ^this is done, I will proceed with the hosting process accordingly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11918.1558793346782%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Oleg Nenashev commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Please follow the Plugin Hosting process: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11913.1558792860262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Please add me as an admin of the repo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199610.1558727311000.11758.1558727580239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Marky Jackson created an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
gitlab-branch-source-plugin
Created:
2019-05-24 19:48
Priority:
Minor
Reporter:
Marky Jackson
For the GSoC project gitlab-branch-source-plugin the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of SCM API}}and {{Branch API Plugins to understand the classes needs to be implemented in GitLab Branch Source Plugin. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it. 3) I have been studing the codebases of ArgelBargel's GitLab Branch Source Plugin, GitHub Branch Source Plugin}}and {{Gitea Plugin. My takeaway was GitLab BS has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example, i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like SCMSource has been broken down to other sub classes , SCMHeadCategory has some different implementation, SCMFileSystem is not implemented, APIs implementation also needs to be changed and the list goes on.. ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new GitLab Branch Source Plugin which will be heavily inspired from Gitea Plugin (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from GitLab Branch Source and GitHub Branch Source Plugins. iii) I will send my compelete list of reasons not to develop the existing GitLab Branch Source Plugin.
