How builds and deployments work

From a git push to a live app: build, deploy, health check, and rollback.

Updated Aug 4, 2026Deployments & CI/CD

When you push code to a branch that has auto-deploy enabled, MonkeysCloud runs a pipeline automatically. Here’s what happens, step by step.

The pipeline lifecycle

  1. Push — your commit arrives in the repository.
  2. Build — MonkeysCloud checks out your code, installs dependencies, runs your test/build commands, and produces a deployable artifact.
  3. Deploy — the artifact is released to the target environment using your chosen deploy strategy.
  4. Health check — MonkeysCloud verifies the app is up and responding.
  5. Rollback — if the health check fails, the previous good deployment is restored automatically.

Why this matters

Because every step is automatic, a broken push never stays broken for long. Either the new version is healthy, or the old one comes back — you don’t have to sit in front of a terminal fixing deploys at 2am.

See it live

Open the project’s Builds page to watch each stage and read the logs. Notifications are sent to Slack, email, or webhooks as configured under notifications.

How builds and deployments work