add a "released dependency check" to release jobs

Description

based on .

When a module release job is run, Jenkins/CI will perform a dependency check against the Central Registry and ensure that all dependencies are proper releases (no pre-releases).

Not in the scope of this isssu: perform the dependecy check at the PR time. This functionality is captured in FOLIO-1715

Note:

This issue focuses on backend dependencies, similar issues is present for NPM library dependencies. Currently any UI module can rely on pre-releases, we should consider running a similar check for those deps.

Acceptance criteria:

  • demonstrate failure by performing a release of a UI module and backend module that depends on unreleased interfaces

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

John Malconian February 26, 2019 at 1:30 PM

Not necessary . This should remain closed.

Aleksandr Arkhipov February 26, 2019 at 1:06 PM

please reopen if it shouldn't be closed

Jakub Skoczen February 6, 2019 at 2:27 PM

Re-open this issue due to a bug in Okapi () that makes the check unsuccessful. Blocked on verification task .

Done

Details

Assignee

Reporter

Priority

Development Team

Core: Platform

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 28, 2018 at 2:49 PM
Updated June 3, 2020 at 4:39 PM
Resolved January 27, 2019 at 10:54 AM
TestRail: Cases
TestRail: Runs