Skip to main content

3.9 Overall flow (create → deploy → feedback)

One release ticket from filing to feedback

momo-cogwork directmomo-ticket-system connectionconnected by bothblocked / guardedsolid = relation · staticdashed = traffic · animated Fill in / import a release ticketPOST /releasesmomo-ticket-systemWithin cutoff time?BlockedCUTOFF_TIME_EXCEEDEDno · and not Deploy / AdminyesView on /releasesTest / production mergeRelease feedbackstatus / urgent / rollbackEdit detailsorder etc.Trigger deploy → Jenkinspipeline callbackPUT /api/ext/releases/id/status

Figure 8 — Full lifecycle of a release ticket: create → merge → deploy → feedback