Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-1938

Create organizations github repositories and add to CI

    XMLWordPrintable

Details

    Description

      Overview:
      There is UXPROD-1544 which requires "vendors" to become "organizations". At the moment there are 3 "vendors" repositories:

      All of these repositories have releases so to not confuse anyone the decision is to create new ones for "organizations" and deprecate vendor-related (instead of renaming).

      The preferred option is to "clone" existing repositories to new ones with history but without tags (i.e. without any information about releases). In case this is not an option, we will copy-paste content manually.

      Please create the following github repositories and associated CI infrastructure (Jenkins/SonarQube/etc.):

      Acceptance Criteria:

      • The three repositories are created and added to the respective teams
      • Members of those teams can create and merge branches
      • CI has been setup for the repositories, including Jenkins builds and SonarQube analysis

      Note: there is FOLIO-1710 which is intended to describe process on how to deprecate existing modules but still in progress. Please let us know if all 3 repositories can be deprecated as part of this ticket or we need to follow some guidelines to do this.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORGSTOR-3 Sample and Reference Data

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORGSTOR-4 Refactor APIs

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORGS-2 Restructure "view details" screen for organizations

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORGS-3 Restructure "create vendor" screen for organizations

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORGS-4 Restructure "edit vendor" screen for organizations

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            has to be done before

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODORGSTOR-2 Project Setup

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORGS-1 Project Setup

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FOLIO-1957 Include mod-organizations-storage and ui-organizations into testing/snapshot environments

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. OKAPI-661 Test effect of module renaming on Okapi dep resolution

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIORG-156 Rename ui-organization

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. FOLIO-1954 Add dev document how to rename a module

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. FOLIO-2014 Exclude vendors app from reference environments

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-1544 Pivot Vendor App into Organizations App

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                dcrossley David Crossley
                piotr_kalashuk Piotr Kalashuk
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases