JFrog Distribution is an on-premise, centralized platform that lets you provision software release distribution. It is a core part of JFrog Enterprise+, managing Release Bundles and their distribution processes, including release content, permission levels, and target destinations.
Distribution provides a secure and structured platform to distribute release binaries to multiple remote locations and update them as new release versions are produced. As part of the release flow, release bundles are verified by the source destination to ensure that they are signed correctly and safe to use.
JFrog Distribution securely manages the distribution of your software releases offering the following benefits:
This chart will do the following:
JFrog Distribution supports any non-Windows platform that can run Docker v1.11 and above, and in addition, has been tested and verified to run as a non-Docker installation on the following 64-bit flavors of Linux:
The high-level distribution flow has two main steps:
A release bundle is created by calling the Create Release Bundle REST API endpoint on JFrog Distribution. This call specifies a variety of parameters including the files comprising the release bundle, and different properties associated with it. Since a release bundle is immutable, any file included in a release bundle cannot be deleted from Artifactory. JFrog Distribution collects the required metadata about the artifacts specified in the request (as an AQL query).
A release bundle is distributed by calling the Distribute Release Bundle REST API endpoint on JFrog Distribution. The distribution is itself split into three steps:
Start a distribution transaction
In this step, JFrog Distribution queries JFrog Mission Control for details on the distribution target nodes. It then primes the target nodes to receive the distributed packages by providing information about distributed files such as their checksum, and providing a GPG key to validate the authenticity of the bundle as a whole.
In this step, JFrog Distribution invokes the Replicator on Artifactory which distributes files over to the target node by replicating them.
In this step, JFrog Distribution notifies the Edge node that the transaction is complete. In turn, the Edge node validates authenticity of the transferred bundle using the GPG key provided when the transaction started. It then validates the integrity of the transferred files by validating their checksum and hosts them in the correct place as specified in the release bundle.
Tell us about a new Kubernetes application
Never miss a thing! Sign up for our newsletter to stay updated.
Discover and learn about everything Kubernetes