added files

2026-08-26 02:02:24 +05:30
parent 58ee8a276a
commit 3419cfba0c
200 changed files with 22132 additions and 0 deletions
@@ -0,0 +1,56 @@
+<!-- m-wiki: type=concept slug=ringmaster-integration topic=deploy base-sha=28f54cf7bef9 generated-at=2026-05-12T00:00:00+00:00 sources=[] -->
+
+> Generated 2026-05-12 at base-sha 28f54cf7bef9. Type: concept. 0 sources.
+
+# Ringmaster / Turbo-Turtle Integration
+
+`deployRingmaster.run()` routes the CI/CD status callback to either Ringmaster or Turbo-Turtle based on which user triggered the build. These are two separate internal systems that track build and deployment state.
+
+## Where it applies in this repo
+
+`src/com/meesho/stages/deployRingmaster.groovy:run`
+
+**Routing decision:**
+```
+build_user = getCause(UserIdCause).getUserId()
+
+if build_user == "ringmaster-bot":
+  POST https://ringmaster-api.meeshogcp.in/api/v1/key/cicd/cd/update
+       (with Authorization: <ringmaster-token> header)
+       payload: hot_fix, job_name, build_no, image, applications, job_status, etc.
+else (turbo-turtle, or other allowed user):
+  POST http://turbo-turtle.meeshogcp.in/api/v1/ci/jenkins/callback
+       payload: repo_name, source_branch, pull_request_number, env, job_name,
+                sub_job_name, build_number, image_tag, build_detailed_error
+```
+
+For `prd`/`int` environments, the base URL is the production Ringmaster API; for `stg`/`ftr`, it uses the admin endpoint.
+
+The Turbo-Turtle payload is written to a temp file first to avoid shell escaping issues with JSON special characters, then passed to `curl -d @<file>`. The temp file is always deleted in a `finally` block.
+
+## Why this design
+
+Ringmaster is the primary orchestration plane for production deployments triggered by human operators via its UI. Turbo-Turtle is the automated CI/CD bot that validates and triggers deployments from PRs. Both need to know when a Jenkins build completes so they can update their state machines.
+
+The `ringmaster-bot` user identity is the distinguishing signal: builds triggered from Ringmaster's UI arrive in Jenkins with that user ID, while Turbo-Turtle-triggered builds arrive with the `turbo-turtle` user ID. The string `"ringmaster-bot"` is load-bearing — if Ringmaster ever renames its bot user, callbacks silently fall through to the Turbo-Turtle endpoint. Never change this string without coordinating with the Ringmaster team.
+
+The Turbo-Turtle JSON payload is written to a temp file (`cicd_payload_${BUILD_NUMBER}_${ts}.json`) to avoid shell escaping failures when payload fields contain single quotes, slashes, or error messages with special characters. The temp file is deleted in a `finally` block.
+
+## Related
+
+- [Notifications](../10-NOTIFICATIONS.md) — notify.groovy calls deployRingmaster
+- [Architecture](../01-ARCHITECTURE.md) — allowedUsers list that includes both bot users
+
+## Sources
+
+(no raw/ sources at bootstrap)
+
+## Notes
+
+<!-- Anything below is human-owned. wiki-init never reads or modifies content under this heading. -->
+
+---
+
+[← Wiki index](../../index.md)
+
+<!-- atomic: keep this page ≤600 words. New scope → new concept page that builds on this one. Do not append paragraphs here. -->