[BUILD-721] Split the webapp into a reactor with two (or more?) submodules Created: 22/Mar/22 Updated: 03/May/22 Resolved: 03/May/22 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Roberto Gomez |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Epic Link: | Release automation | ||||||||
| Description |
|
One which is the API: communication layer, responsible for technical details, talks to Nexus/Jira/Bitbucket/Jenkins. Name = magnolia-mgmt-api And the other one which consume it: adds business value, for instance: 'I want to run a CVE scan every night on repository X to make sure there is no security flaw discovered there.' Because the jobs are pretty simple (more or less direct calls to the APIs) maybe all the consumers can be grouped into the same artifact (name = magnolia-mgmt-services # 0 0 0 * * * java -jar magnolia-mgmt-services.jar DailyCveScans # 0 0/15 8-20 * * MON-FRI java -jar magnolia-mgmt-services.jar PostReleaseService etc. |