CI/CD Separation
Overview
Separate JFrog Platform deployments for continuous integration and continuous delivery, so development stays off the production site.
Why
- CI and CD teams have different workflows and infrastructure needs
- 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 one deployment for CI and another for CD
- CI covers build, test, and release. CD covers distribution and production deploy
- Each site is owned and managed by its own team
- Repository federation promotes only production-ready packages from CI to CD. 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. Self-managed Platform Federation is in early access
- The CD deployment is the single source for production environments
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.
