Complete the SDLC - Release Bundles, Edge Nodes. Build Integration
In addition to the core Artifactory artifact management service and tools for user and project management, the JFrog Platform includes additional components and services that cover other phases of the CICD process.
The components and services described in this section are available with an Enterprise+ license.
JFrog Distribution
JFrog Distribution lets you provision, launch, and track the Distribution stage of the Software Development Life Cycle (SDLC).
Release Bundles are collections of artifacts and binaries you create from the repositories of your development project. When the release process starts, bundle content is locked and signed to secure its content from modification during distribution.
The release bundle is securely distributed to JFrog SaaS Cloud and Self-hosted nodes in your subscription.
Edge Nodes are Self-managed JFrog servers that you can install to support delivery to remote locations.
JFrog release definition and distribution
Release definition on the JFrog Platform
JFrog’s release model centers on immutable, signed units of software. The modern unit is Release Bundle v2 (RBv2). Release Bundle v1 is legacy.
The product area for stages, promotion, evidence, and optional distribution is Release Lifecycle Management (RLM). Overview: Release Lifecycle Management.
Core components
| Piece | Role in releases |
|---|---|
| Artifactory | Stores binaries and metadata; repos map to lifecycle stages. |
| Xray | Policy and scanning; can block promotion and (with the right tier) block distribution. |
| JFrog CLI / REST | Automate create → promote → distribute. |
| JFrog Pipelines (optional) | CI/CD; can add approval gates on steps. |
Defining a Release Bundle (v2)
A Release Bundle is a named, versioned set of artifacts representing a release candidate or release.
Ways to create RBv2:
- Platform UI
- REST (e.g.
POST /lifecycle/api/v2/release_bundle) - JFrog CLI — Release Lifecycle Management CLI
Admin workflow (stages, repos, lifecycle, keys, webhooks): Release Lifecycle Management Workflow.
Distributing a Release Bundle (v2)
Distribution replicates release content to remote points (often Edge nodes).
Typical flow:
- Create RBv2
- Promote through stages
- Distribute (e.g.
POST /lifecycle/api/v2/distribution/distribute/{name}/{version})
Air gap: Distribute Release Bundle v2 Versions in an Air Gap Environment.
Inflection points and approvals
- Xray policies — automated block on promote/distribute (tiers per JFrog docs in the RLM page above).
- RBAC / Projects — who may create, promote, distribute.
- Evidence — signed attestations: Evidence Management.
- Webhooks — external approval/integration hooks (see workflow doc).
- Pipelines approval gates — human gates in CI/CD: Approval Gates.
Edge node
An Edge node is a remote endpoint (commonly used with distribution) that receives and serves release content near consumers, under trust/signing setup from the main platform.
Glossary (selected JFrog terms)
| Term | Short meaning |
|---|---|
| AQL | Artifactory Query Language |
| BuildInfo | Build metadata from CI |
| Circle of trust | Trust between platform deployments |
| Evidence | Signed lifecycle action metadata |
| JPD | JFrog Platform Deployment |
| Lifecycle / stages | DEV/STG/PROD-style phases with repo mapping |
| Promotion | Move materialization of bundle content for a stage |
| Scoped tokens | Fine-grained access tokens |
| Federation | Cross-instance repo federation (distinct from RB→Edge distribution) |
Corporate rollout pattern (short) Standardize stages and repo mapping. Treat RBv2 as the release contract. Enforce Xray at promote / distribute boundaries. Use RBAC / Projects so only release roles reach production stages. Optionally distribute to Edge for regional or regulated footprints. Use webhooks and evidence for ITSM and audit trails.