PR build pipeline for platform-core releases

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

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

John Malconian March 21, 2019 at 3:30 AM

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.

John Malconian March 18, 2019 at 8:35 PM
Edited

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

John Malconian February 28, 2019 at 1:43 PM

Jakub Skoczen February 28, 2019 at 11:29 AM

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!

Jakub Skoczen February 26, 2019 at 12:58 PM

Is platform-core blocked on mod-finance-storage and mod-vendors?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 25, 2019 at 1:37 PM
Updated June 3, 2020 at 4:39 PM
Resolved March 21, 2019 at 1:07 PM
TestRail: Cases
TestRail: Runs

Flag notifications