The following table displays the supported features and function for Distribution according to the required environment.
Feature | SaaS | Self-Hosted | ||
---|---|---|---|---|
Comprehensive REST API | ||||
Set Access Permissions | ||||
Create Release Bundles | ||||
Optimized Replication | ||||
Auditing and Traceability | ||||
Secured & Protected Release Bundles | ||||
Edge-based Software Distribution | ||||
|
| |||
| ||||
Third-Party Access (Read-Only) |
|
|
The high-level distribution flow has two main steps:
Creating a Release Bundle
A Release Bundle can be created in the JFrog Platform webUI or by calling the Create Release Bundle REST API endpoint in 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 - they are automatically copied and saved into the Release Bundle separate repository where their contents cannot be edited or removed. JFrog Distribution collects the required metadata about the artifacts specified in the request by using an AQL query.
To scan your Release Bundle by JFrog Xray, the Release Bundle must first be declared as an indexed resource. For more information, see Indexing Resources |
Distributing a Release Bundle
A release bundle can distributed in the JFrog Platform WebUI or by calling the Distribute Release Bundle REST API endpoint in JFrog Distribution.
Setting a Watch on a Release Bundle containing a Policy set with a Block Distributing action, will automatically block distributing the infected Release Bundle based on the Xray scanning results. For more information, see Distributing Release Bundles . |
The distribution process includes the following steps: