Skip to main content

5 · Quick reference: which systems does one action call

User actionSystems called, in order
(cogwork) open the release listmomo-ticket-system (ext, GET)
(cogwork) expand a release ticket's detailsmomo-ticket-system (ext, GET)
(cogwork) click a system to open the Jenkins panelmomo-ticket-system (ext, GET job list) → Jenkins (direct trigger / poll)
(cogwork) save release feedbackmomo-ticket-system (ext, PUT feedback)
(cogwork) apply one Config Server changemomo-ticket-system (ext, GET latest record) → RCM (POST /config, one to three environments) → momo-ticket-system (ext, PUT mark done)
(cogwork) check for updates at startupGitLab (the project's own Releases API)
(cogwork) work on MRs in the GitLab tabGitLab (direct)
(cogwork) ITSM: query Jira / create GitLab issuesAtlassian (query) → GitLab (create issue)
(web) SSO sign-inmomo-ticket-system → Zitadel → momo-ticket-system (issues JWT)
(web) fill in / import a release ticketmomo-ticket-system (JWT, POST)
(web) test merge / production mergemomo-ticket-system → GitLab (server-side git merge/push)
(web) trigger deploymomo-ticket-system → Jenkins (trigger); the result comes back from the pipeline over the ext API
(web) release feedbackmomo-ticket-system (JWT, PUT feedback)
(web) submit a Config Server changemomo-ticket-system (JWT, POST) — the apply step is done later by cogwork