Released: August 19, 2019
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.
From release 1.7, Distribution runs on top of Ubuntu 16.04.
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.
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: 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.
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
Released: January 9, 2019
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
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.
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
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.
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.
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:
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
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.
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, the Distribution services fetch the proxies configuration which are required to perform communication.
Released: August 29, 2018
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.
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.
You can create complex queries by specifying a range of properties using the condition toggle with the And | Or options.
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.