Details
-
Improvement
-
Resolution: Done
-
Neutral
-
None
-
None
-
None
-
None
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
) and each cron job would call a different process, e.g.:
# 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.
Checklists
Acceptance criteria
Attachments
Issue Links
- is depended upon by
-
BUILD-745 Move the webapp to Fargate
-
- Closed
-