[FOLIO-1631] add a "released dependency check" to release jobs Created: 28/Nov/18 Updated: 03/Jun/20 Resolved: 27/Jan/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, platform-backlog, sprint52, sprint53, sprint54, sprint55 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| 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
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:
|
| Comments |
| Comment by Jakub Skoczen [ 06/Feb/19 ] |
|
Re-open this issue due to a bug in Okapi (
|
| Comment by Aleksandr Arkhipov [ 26/Feb/19 ] |
|
John Malconian please reopen if it shouldn't be closed |
| Comment by John Malconian [ 26/Feb/19 ] |
|
Not necessary Aleksandr Arkhipov. This should remain closed. |