[FOLIO-728] publish ModuleDescriptors to the central registry for a new release Created: 18/Jul/17  Updated: 12/Nov/18  Resolved: 21/Aug/17

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

Type: Task Priority: P2
Reporter: Jakub Skoczen Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: ci, sprint19, sprint20
Remaining Estimate: Not Specified
Time Spent: 4 hours, 55 minutes
Original estimate: Not Specified

Issue links:
Blocks
blocks OKAPI-350 upgrade all modules in an Okapi instance Closed
is blocked by FOLIO-708 set up a central Okapi instance for s... Closed
is blocked by FOLIO-768 Fix the Descriptor discrepancies Closed
is blocked by FOLIO-777 Jenkins needs 'gradle generateDescrip... Closed
Relates
relates to FOLIO-793 Use mod descriptors from repository i... Closed
relates to FOLIO-799 Post UI module descriptors to mod des... Closed
relates to OKAPI-376 add ability to sort and retrieve late... Closed
relates to FOLIO-701 generate Module and Deployment Descri... Closed
relates to FOLIO-700 set up a central repository of Module... Closed
Sprint:

 Description   

During a release (performed by Jenkins) push the module descriptor for that version to the central repository.



 Comments   
Comment by Jakub Skoczen [ 02/Aug/17 ]

We have discussed on the call publishing also snapshot MDs, for this purpose the build will append orderable build number to the version number.

Comment by David Crossley [ 02/Aug/17 ]

Done mod-configuration for FOLIO-701 Closed , so its generated ModuleDescriptor is now ready.

Comment by Wayne Schneider [ 15/Aug/17 ]

Set up model Jenkins job for mod-notes

Comment by Wayne Schneider [ 17/Aug/17 ]

Set up and tested mod-authtoken. Error with mod-configuration (ModuleDescriptor.json not generated in the right place?)

Comment by David Crossley [ 18/Aug/17 ]

We discussed mod-configuration on Slack. It is deliberately generated into top-level ./target/ModuleDescriptor.json as for all other maven-related modules, rather than into mod-configuration/mod-configuration-server/target

Comment by Wayne Schneider [ 18/Aug/17 ]

One issue that this raises – there are dependency issues between modules that can cause the publishing of mod descriptors to fail. For example, in my testing, I tried to publish the mod-users-bl mod descriptor before the mod-users mod descriptor, and Okapi rejected it (because the users interface was not registered). Adam Dickmeiss – do you think this is a problem, or is this more or less as designed for the central registry? I'm on the fence about it, I can see arguments both ways.

Comment by Wayne Schneider [ 18/Aug/17 ]

Complete for all non-pipeline snapshot jobs and all release jobs.

Comment by Wayne Schneider [ 18/Aug/17 ]

Completed pipeline jobs for mod-circulation-storage and mod-inventory-storage

Comment by Adam Dickmeiss [ 18/Aug/17 ]

Wayne Schneider : Rejecting MDs with unsatisfied "requires" was intended.

Great that pipelining is in the works.

Comment by Wayne Schneider [ 21/Aug/17 ]

All active backend module projects now publish their mod descriptors to the registry.

Comment by Jakub Skoczen [ 29/Aug/17 ]

Wayne Schneider what about the ui modules? – I found FOLIO-799 Closed

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