Using the latest JFrog products?
JFrog Platform User Guide
Released: January 8, 2020
Easier Inclusion of Docker Images within a Release Bundle
When creating a new Release Bundle, it is sufficient to specify query criteria that will match the manifest.json of the desired docker image. Distribution will include all the Docker layers of the Docker image associated with that manifest.json file. For more information, see the Including Docker Images in a Release Bundle section.
- In certain scenarios, Distribution tasks did not complete, if Distribution or the machine restarted during the distribution process.
- In certain scenarios, Distribution tasks did not complete, if they contained a large number of artifacts.
- Distribution tasks hung in Pending Distribution status, if one of the Distribution nodes contained a malfunctioning distributor or Redis service.
- In Linux native installations, Distribution did not restart after a machine reboot, since the Redis service was not configured to restart after machine reboots.
- In certain scenarios, the UI was unable to display the Distribution Tracking tab after upgrading Distribution from a version prior to 1.7.3.
Released: April 5, 2020
Immediate Abort for all distribution tasks
Administrators can now perform an immediate abort of all running distribution tasks using the Stop All Tasks REST API.
- Deleting release bundles from JFrog Distribution will now work asynchronously.
- A timeout for deletion of release bundle version from source Artifactory is configurable now via
- Fixed permission issues in Distribution Docker images.
- Fixed an issue where the same "Distributor not available" exception was returned multiple times, making the log file size large.
- Improved edge node discovery by refreshing the Mission Control cache information to Distribution.
- The default limit of allowed artifacts in a single Release Bundle is now set to 3,000. This is configurable using the
Released: 26 May, 2020
Release Bundle Distribution Process is Asynchronous
The entire Release Bundle distribution process to the Edge nodes is now asynchronous providing optimized performance and stability. To gain the full benefit of this improved process, you need to upgrade to Artifactory version 6.20.
- Fixed an issue whereby, JFrog Distribution access tokens leak was experienced within an Artifactory HA cluster deployment. Please note that the fix is on the Artifactory side, so be sure to upgrade to JFrog Artifactory version 6.20.
- Fixed an issue whereby, the Release Bundle “In-Progress” status was generated for all distribution issues. This general state has been replaced with specific states to accommodate different distribution issues.
- Fixed an issue whereby, spaces in artifact name or repository path added to AQL queries as part of the Release Bundle creation process were truncated during the distribution process.
Released: July 5, 2020
Distribution Load Balancing Mechanism Improvements
Improved the load balancing mechanism in High Availability environments.
- Fixed an issue whereby, an incorrect Release Bundle version status was displayed in the web UI if the Distribution process was aborted, in pending or aborted in progress.
- Fixed an issue whereby, under certain circumstances, the Distribution service lost pairing with the Authentication Provider.
Released: August 19, 2019
Increased the Number of Distributed Binaries in a Release Bundle
We have significantly increased the number of binaries that can be included in a release bundle version.
To manage large Release Bundles you need to upgrade to Artifactory 6.12.
Ubuntu 16.04 Support
From release 1.7, Distribution runs on top of Ubuntu 16.04.
2k Key Certificates are Required for Signing Release Bundles
To increase security, we now require the Signing Keys to be at least 2K. If you are using a smaller GPG key, you will now need to update your GPG keys when upgrading to Distribution 1.7.
For backward compatibility, Release Bundle versions that were previously signed using a smaller GPG key than 2K will still be distributed.
Token Expiration Time is Set to 180 Minutes
The access token expiration time is set by default to 180 minutes.
- The request_header_max_size can manually be increased to prevent receiving an HTTP 400 message when signing in to Distribution using SSO.
Released: September 23, 2019
- Release Bundle distribution stuck when the process for storing the Release Bundles in the source Artifactory failed.
- Improved the socket timeout mechanism between JFrog Distribution and the Artifactory Edge nodes.
Released: October 03, 2019
- Fixed an issue where aborting distribution of very large release bundles was time consuming and blocked the processing of additional distributions.
Released: October 17, 2019
Released: February 17, 2019
This version adds the capability for JFrog Distribution to send usage data to JFrog. This data will only be used to analyze how different features are used to allow continuous improvement of the product.
You may switch sending data on or off using the new Update System Settings REST API endpoint.
Optimized Support Process
When requesting support, you are now able to create Support Bundles that provide critical system information that help JFrog support staff resolve issues you are having.
Following large-scale environment testing, JFrog Distribution queuing mechanism works much faster providing an overall improvement in performance.
Released: June 27, 2019
- Fixed an issue where in some cases running Distribution as a cluster in Kubernetes had an internal connectivity issue, which caused the Distribution service to stay in not ready state.
Released: January 9, 2019
Block the Distribution of Release Bundles with Vulnerabilities
To prevent the distribution of release bundles that contain artifacts with issues or vulnerabilities, JFrog Distribution will now prevent signing a release bundle if it includes an artifact that has been blocked for download by JFrog Xray. Once an artifact triggers a violation in Xray and is blocked for download, Distribution will provide a corresponding indication in various screens if your release bundle includes a blocked artifact, and issue an error message if you attempt to sign "infected" release bundles.
Distribution HA has been improved to provide better performance for high load bursts, and faster recovery when a cluster node goes down.
When selecting repositories from which to extract artifacts for the release bundle, Distribution now presents a list for you to choose from. You can also type the repository name, and Distribution will display a list the matches your input.
You can now select multiple release bundles for redistribution with a single action.
Released: February 5, 2019
Simplified Distributor Microservice Installation for Kubernetes and Docker
From this version, the Distributor microservice does not need to be preset with an access token when being installed. The microservice fetches an access token from the Redis database when needed.
Optimized Release Bundles Page Performance
A performance bottleneck that caused the Release Bundle page to work very slowly has been eliminated in this version so the page now works much faster.
Released: December 12, 2018
MongoDB Replaced with a Relational Database
To simplify the Distribution installation and upgrade process, Distribution has replaced its use of MongoDB with PostgreSQL. This will also facilitate the support of additional relational database in the future.
Hardened Security for Secrets
To harden security when providing sensitive configurations (secrets) such as credentials for third party services (e.g. databases that Distribution uses), they may be placed in a temporary file. Distribution will load the parameters specified in the file at startup and then delete the file.
Path Mapping Templates
As a convenience, this version introduces a set of commonly used templates you can use to set up the path mappings that govern where files form the source Artifactory service are hosted in the target. Currently, the templates provided make it easy to create the following mappings:
- Moving files from a specific repository in the source Artifactory service to a different repository in the target
- Moving files into a specific folder in the corresponding repository in the target
- Moving files from a specific folder in the source, to a different folder in the corresponding repository in the target
Health Check API
The Test Connection REST API endpoint will now provide error information if any of the databases required by Distribution are not functioning correctly.
Released: October 11, 2018
Enhanced Release Bundle Content Protection
This release includes an additional layer of protection on the contents in your release bundles. Previously, the distribution process failed if artifacts in a release bundle were edited or removed from the source repository in Artifactory. As part of the release bundle signing process, Distribution will now trigger Artifactory to clone the contents of a release bundle into an isolated release-bundles repository.
Deploying your GPG Key
Improved Distribution Proxy Management
In conjunction to the release of Mission Control 3.2, this release supports assigning proxy for Distribution services on the site level. As part of the release, proxy settings are automatically inherited to all services including the Distribution service thereby removing the need to assign a proxy separately for each service in the site. Using Mission Control Proxy Management , the Distribution services fetch the proxies configuration which are required to perform communication.
Released: August 29, 2018
Distribution High Availability
You can now scale your Distribution environment with as many nodes as you need. This enhances Distribution’s performance by delegating all workload across available cluster nodes, through a load balancer. JFrog Distribution 1.2 introduces a highly available active-active cluster architecture, ensuring continuous security and governance to your software packages.
High Availability supports:
Improved Performance and Resilience: You can now scale your Distribution environment with as many nodes as you need. This enhances Distribution performance by delegating all workload across available cluster nodes, through a load balancer.In case one or more nodes is unavailable or down for an upgrade, the load is shared between the remaining nodes, ensuring optimal resilience and uptime.
- Automatic Synchronization: Distribution seamlessly and instantly synchronizes all data, configuration, cached objects and scheduled job changes across all cluster nodes.
The "Open" State Supports Creating Release Bundles Progressively
The new release bundle 'Open' status lets you 'Create' and 'Save' your release bundles in 'Open' status mode allowing you to click 'Save & Sign' only when you are ready to distribute the bundle.
The Create & Sign button replaces the previous 'Create' button to immediately create, sign and distribute the bundle.
Expanded Properties Query Capabilities in the Query Builder
You can create complex queries by specifying a range of properties using the condition toggle with the And | Or options.
Support for Microsoft Internet Explorer 11
Distribution has been tested on IE 11.
Released: July 2, 2018
Release bundle management has been enhanced to provide better visibility of release actions and easier definition of release bundle content.
Simple Query Builder: Previously, you could only specify the release bundle content using an AQL query. This has been supplemented with a simple form through which you can specify repository names, build names and numbers as well as include and exclude patterns to specify release bundle content. These specifications are automatically translated into an AQL query which you can also view.
Viewing Release Bundle Details: The release bundle details view has been reorganized and enhanced. A new Spec tab provides all the parameters used to create the release bundle, and a new Content tab provides details of the artifacts and builds in a bundle as well as the release bundle metadata.
For more details on these enhancements, please refer to Release Bundles.