[JIRA] (JENKINS-57539) Prepare design document for a top level architecture

29 views
Skip to first unread message

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 6:58:01 AM5/18/19
to jenkinsc...@googlegroups.com
Parichay Barpanda created an issue
 
Jenkins / Story JENKINS-57539
Prepare design document for a top level architecture
Issue Type: Story Story
Assignee: Mark Waite
Components: branch-api-plugin, git-plugin, gitlab-api-plugin, gitlab-branch-source-plugin, gitlab-plugin, pipeline-multibranch-defaults-plugin, scm-api-plugin
Created: 2019-05-18 10:57
Environment: Google Docs
Labels: gsoc-2019
Priority: Minor Minor
Reporter: Parichay Barpanda

This issue is about preparing a design document of a top level architecture for the plugins that will be developed in the 'Multibranch Pipeline Support for GitLab' Project.

  • Objectives and expectations based on proposal
  • Answer questions such as
    • "How is the user going to use this?",
    • "What configurations are needed?", 
    • "What are the components of the plugin?"
  • Create diagrams of API
  • Write mini user guides as if project is already done

After completion, reality mapping shall be done by a discussion with the key stakeholders in other Branch Source Plugins.

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:00:02 AM5/18/19
to jenkinsc...@googlegroups.com

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:00:02 AM5/18/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
This issue is about preparing a design document of a top level architecture for the plugins that will be developed in the 'Multibranch Pipeline Support for GitLab' Project.
* Objectives and expectations based on proposal
* Answer questions such as
** "How is the user going to use this?",
** "What configurations are needed?", 
** "What are the components of the plugin?"
* Create diagrams of API
* Write mini user guides as if project is already done


After completion, reality mapping shall be done by a discussion with the key stakeholders in other Branch Source Plugins.

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:00:02 AM5/18/19
to jenkinsc...@googlegroups.com

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:01:01 AM5/18/19
to jenkinsc...@googlegroups.com

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:01:01 AM5/18/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
Change By: Parichay Barpanda
Sprint: GSoC 2019. Coding Phase 1 3

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 7:05:02 AM5/18/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
Change By: Parichay Barpanda
Sprint: GSoC 2019. Coding Phase 1 Community Bonding

mark.earl.waite@gmail.com (JIRA)

unread,
May 18, 2019, 8:42:03 AM5/18/19
to jenkinsc...@googlegroups.com
Mark Waite commented on Story JENKINS-57539
 
Re: Prepare design document for a top level architecture

There are several good documents available that can be used as the starting point, including:

parichay.barpanda@gmail.com (JIRA)

unread,
May 18, 2019, 8:47:01 AM5/18/19
to jenkinsc...@googlegroups.com

Thanks Mark. I was already referring to the SCM API and BRANCH API docs. They are verbose and gives a nice picture of how the implementation will be done. I'll check rest of the pointers for more info.

parichay.barpanda@gmail.com (JIRA)

unread,
May 19, 2019, 4:04:03 PM5/19/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
Change By: Parichay Barpanda
This issue is about preparing a design document of a top level architecture for the plugins that will be developed in the 'Multibranch Pipeline Support for GitLab' Project.
* Objectives and expectations based on proposal
* Answer questions such as
** "How is the user going to use this?",
** "What configurations are needed?", 
** "What are the components of the plugin?"
* Create diagrams of API
* Write mini user guides as if project is already done

After completion, reality mapping shall be done by through a discussion with the key stakeholders in other Branch Source Plugins.

parichay.barpanda@gmail.com (JIRA)

unread,
May 19, 2019, 4:05:02 PM5/19/19
to jenkinsc...@googlegroups.com
Parichay Barpanda started work on Story JENKINS-57539
 
Change By: Parichay Barpanda
Status: Open In Progress

parichay.barpanda@gmail.com (JIRA)

unread,
May 28, 2019, 2:47:02 PM5/28/19
to jenkinsc...@googlegroups.com
 
Re: Prepare design document for a top level architecture

The document is being created as the implementation are done.

parichay.barpanda@gmail.com (JIRA)

unread,
May 28, 2019, 2:58:02 PM5/28/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated Story JENKINS-57539
 

Some important implementation of classes has been added to the document from the SCM API and Branch API docs. Unfortunately couldn't find more support for design document from any experienced developer of any Branch Source Plugin but with the help of well maintained codebase and javadocs I was able to come up with my versions of implementations idea. The design document doesn't provide a concrete idea of our plugin APIs but it will be updated throughout the course of development. So at the end of the plugin release, this design document will contain all the necessary information a user or other plugin authors require to extend or get inspired.

Change By: Parichay Barpanda
Status: In Progress Fixed but Unreleased
Resolution: Fixed

parichay.barpanda@gmail.com (JIRA)

unread,
May 28, 2019, 2:58:03 PM5/28/19
to jenkinsc...@googlegroups.com
Parichay Barpanda updated an issue
Change By: Parichay Barpanda
Comment:
The document is being created as the implementation are done.

marky.r.jackson@gmail.com (JIRA)

unread,
May 30, 2019, 11:33:01 PM5/30/19
to jenkinsc...@googlegroups.com
Marky Jackson commented on Story JENKINS-57539
 
Re: Prepare design document for a top level architecture

Per team agreeable, this document is meeting acceptance. Parichay Barpanda says he would like to add a few more items to this body of work. I will leave open until then but it is agreed that this can be closed once that is done.

mark.earl.waite@gmail.com (JIRA)

unread,
Apr 4, 2020, 8:41:02 PM4/4/20
to jenkinsc...@googlegroups.com
Mark Waite updated an issue
 
Change By: Mark Waite
Component/s: git-plugin
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages