[FOLIO-2878] SPIKE: investigate "layered" jar concepts for quick rollout of RMB Created: 17/Nov/20 Updated: 26/Nov/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | CP: Non-roadmap backlog |
| Development Team: | Core: Platform |
| Description |
|
Context We need a simple way to rollout Docker images for a bunch (all) Folio modules that use RMB to aid integration testing on custom environments. We'd like to be able to avoid releasing unverified bugfix RMB releases and subsequently re-releasing all FOLIO modules or creating custom branches in all module Git repos. Preferably there is a build time solution that be executed solely by operational folks. For the sake of simplicity the assumption here is that bugfix RMB version is fully compatible with version originally shipped with the module. It would be great if this could also simplify security updates. Tools There are some tools available that could help. FOLIO modules docker images can have a more flexible internal structure, e.g a "layered jar" instead of "fat jar", to help with rebuilding them and replacing selected library dependencies. Layered jar concept has been introduced in Sprint Boot https://medium.com/techwasti/spring-boot-cloud-native-buildpacks-and-layered-jars-bbe74f80e983 A similar approach can be achieved with the Jib maven plugin: https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin |