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

PR build pipeline for platform-complete releases

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Core: Platform - Sprint 60
    • Story Points:
      3
    • Development Team:
      Core: Platform

      Description

      Description:

      1. when a new PR is created a PR build is initiated (folio-complete-release-{pr_number}). Note: the backend dependencies must be resolved using releases only (NO pre-releases/snapshots).
      2. if the build is successful and UI integration tests pass, new UI module dependency along with a list of backend modules and yarn.lock is committed to the stable release branch.

      Out of scope:

      building and deploying new environment from a stable release branch

      Acceptance criteria:

      1. Jenkins must provide information about the build status (success/failure) on the PR and a link to the build job
      2. In case of failures the following artifacts must be archived in Jenkins: UI bundle, yarn.lock, okapi-install.json

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                malc John Malconian
                Reporter:
                jakub Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases