[FOLIO-1738] PR build pipeline for platform-core releases Created: 25/Jan/19  Updated: 03/Jun/20  Resolved: 21/Mar/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1577 Automated builds for FOLIO 'release' Closed
blocks FOLIO-1739 PR build pipeline for platform-comple... Closed
blocks FOLIO-1869 Q1 platform-core platform-complete re... Closed
blocks FOLIO-1742 build and deploy platform-core/master... Closed
is blocked by CIRCSTORE-103 use loadSample to load sample data Closed
is blocked by CIRCSTORE-104 use loadReference to load reference data Closed
is blocked by FOLIO-1834 Implement FOLIO-1738 scaffolding in J... Closed
is blocked by FOLIO-1851 review a local set up of 'platform-co... Closed
is blocked by MODINVSTOR-264 use loadSample to load sample data Closed
is blocked by MODLOGIN-105 use loadSample to load sample data Closed
is blocked by MODPERMS-50 use loadSample to load sample data Closed
is blocked by MODTAG-14 use loadReference to load reference data Closed
is blocked by MODTAG-15 use loadSample to load sample data Closed
is blocked by MODUSERS-103 use loadSample/loadReference to load ... Closed
is blocked by MODINVSTOR-270 service points user sample data Closed
Relates
relates to FOLIO-1840 SPIKE: Determine best method to expir... Closed
relates to MODINVSTOR-263 Update reference data when upgrading Closed
Sprint: Core: Platform - Sprint 56, Core: Platform - Sprint 59
Story Points: 5
Development Team: Core: Platform

 Description   

Description:

1. when a new PR is created a PR build is initiated (folio-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 (master).

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



 Comments   
Comment by John Malconian [ 04/Feb/19 ]

One of the issues that would cause PR builds to fail is the loading of sample data. Since backend modules are pulled into a build via dependency resolution, backend module versions are dynamic but sample data loading in folio-ansible is configured statically. The result would be sample data mismatches between what's configured in folio-ansible vs the sample data that exists for a given tagged module in Github. In order to avoid this inevitable problem, all reference and sample data should be loaded via the module during tenant initialization. Modules with reference and sample data in platform-core include:

  • mod-inventory-storage
  • mod-circulation-storage
  • mod-tags
Comment by Jakub Skoczen [ 07/Feb/19 ]

John Malconian I have added issues for loading reference/sample data for mod-circulation-storage, mod-inventory-storage and mod-tags. Is this task blocked until those issues are resolved?

Comment by Aleksandr Arkhipov [ 22/Feb/19 ]

Moving out of sprint 57 as it is blocked

Comment by Jakub Skoczen [ 26/Feb/19 ]

Ian Hardy John Malconian Is platform-core blocked on mod-finance-storage and mod-vendors?

Comment by Jakub Skoczen [ 28/Feb/19 ]

John Malconian during the sprint planning meeting we have discussed that this issue is blocked for completion but not blocked for progress and that you will create a seperate ticket to capture the tasks that can be done in the meantime. Could you please create the ticket, link it here as blocker and add to Sprint 58? Thanks!

Comment by John Malconian [ 28/Feb/19 ]

Jakub Skoczen FOLIO-1834 Closed

Comment by John Malconian [ 18/Mar/19 ]

Outstanding bugs/items with platform build.

  • CI build still 'passes' even when regression tests fail and exit 1.
  • Charge target FOLIO URL to instance instead of local bundle.
  • Commit yarn.lock and install.json files to master
Comment by John Malconian [ 21/Mar/19 ]

Only one remaining issue with CI pipeline: Need to detect whether to abort pipeline early in the build based on last commit message in order to avoid firing off unnecessary PR builds.

Generated at Thu Feb 08 23:15:33 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.