Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-05

CI/CD — from Development to Production

Two environments, a pipeline with validation and approval, one-click rollback and, if you want, your own Git repository.

On this page (3)

CI/CD is an add-on available separately, on any plan.

CI/CD separates where you build (Development) from where the business uses it (Production). You change pipelines, transformations, dashboards, agents, notebooks, flows and clusters in Development, check them, request the send and someone else approves. Only then does Production change — and if something goes wrong, Roll back returns Production to how it was.

What you get#

  • Two environments with separate data. Development has its own datasets (dev_<customer>_bronze, _silver, _gold); Production uses prd_<customer>_*.
  • A standard pipeline, always the same: change → version → validate → approval → deploy → check. See The standard pipeline.
  • Real approval. Whoever requests the send never approves their own request.
  • One-click rollback, with Production restored to its previous state.
  • Your Git repository (optional) — GitHub or GitLab (or Azure DevOps). See Connect the repository.
  • Per-person access in each environment, with ready-made profiles. See Approvers and access.

Get started in three steps#

  1. 1. Create Development

    In ETL/ELT → CI/CD, Environments section, use Create development environment. Production definitions are copied; data and credentials are not.

  2. 2. Build in Development

    Switch environments in the top switcher (Development | Production). A yellow bar reminds you that you are in Development.

  3. 3. Send to Production

    Back in CI/CD, the list shows what changed. Use Send to production; the pipeline validates, asks for approval and deploys.

CI/CD screen with what is ready to send, the Send to production button, the history of sends and the Environments section

Read more#

Related links