Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Core: Platform - Sprint 60
-
3
-
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
- blocks
-
FOLIO-1577 Automated builds for FOLIO 'release'
-
- Closed
-
- is blocked by
-
FOLIO-1738 PR build pipeline for platform-core releases
-
- Closed
-
-
FOLIO-1797 SPIKE: establish which platform-core modules require loadSample and loadReference support
-
- Closed
-
-
MODFISTO-5 use loadSample/loadReference to load sample and reference data
-
- Closed
-
-
MODVEND-81 Load sample data via tenant API
-
- Closed
-
-
MODVEND-92 use loadSample/loadReference to load sample and reference data
-
- Closed
-
- relates to
-
FOLIO-1840 SPIKE: Determine best method to expire and clean up FOLIO instances
-
- Closed
-