Skip to main content

CI/CD Separation


Overview

Separate JFrog Platform SaaS sites for continuous integration and continuous delivery, so development stays off the production site.

Why

  • CI and CD teams have different workflows, so each site can follow its own
  • Isolating build from deployment, and limiting who can reach the CD site, reduces accidental or unauthorized production releases
  • Production can be held to stricter compliance controls than development
  • High-frequency CI load stays off the production site
  • Production binaries live only on the CD site, which simplifies audit

How

  • Run separate sites for CI and CD. Each site is owned by its own team
  • CI covers build, test, and release. CD covers distribution and production deploy
  • Repository federation promotes only production-ready packages from CI to the CD site. Sites can be in different cloud providers and regions. Platform Federation syncs the whole project and access model, with no per-entity filter, so use it when the CI and CD sites should share that model
  • The CD site is the single source of production binaries

Architecture

The following is a schematic high-level architecture of this topology, with two organizations each having a dedicated CI site that federates production releases to a common CD site.

CI/CD Separation CI/CD Separation