Released: 29 September, 2020
Peer-to-Peer (P2P) Download
The new Peer-to-Peer (P2P) Download feature allows hosts to download artifacts from local, remote, and virtual repositories through a local network of peers in addition to downloading artifacts from JFrog Artifactory. Downloading files using P2P provides the following benefits:
Handles bursts of downloads from Artifactory.
Improves the download speed and decreases bandwidth consumption.
Promotes the scalability and availability of your artifact downloads while providing a highly secure environment.
P2P download is supported in the JFrog Platform in a self-hosted environment and requires a JFrog Enterprise+ subscription.
GraphQL API for the JFrog Platform Metadata
JFrog's Metadata Service public APIs are now enabled allowing you to query the entities from the metadata server with GraphQL.
JFrog now offers tools that enable a real-time view of the platform’s operation through various analytics and visualization tools.
Changes in Artifactory to Facilitate the New Docker Rate Limit
Following the latest Docker announcement regarding changes to the Docker Rate Limits, Artifactory 7.9 includes several internal improvements to support the usage of remote repositories opposite Docker Hub while taking into account the new rate limits. In order to use your Docker account type, you need to authenticate the Docker Hub pull requests, by setting your user and password in your Advanced Remote Docker Repositories.
Docker Remote Repository Improvements
Docker Schema 2 is now fetched from the remote registry if no header was sent. This improves the Docker experience when the metadata expires.
Docker Pull Performance Improvements
Greatly improved the performance of Docker pull requests by digest and by tag. From 7.9, Artifactory will use more efficient queries and better utilize the internal caching when serving Docker pull requests.
Viewing and Tracking Non-Revocable Access Tokens
You can view and track non-revocable Access Token in the UI. You can now filter the token view based on the token's revocability and not just its expiry. The behavior for a token revocation request also changed, and you will now see an error message if you try to revoke a non-revocable token. Token revocability is still governed by its expiry and the
Improved the Monitoring JFrog Microservices Status Page in the UI
The Service Statuses page in the UI displays an improved view with detailed information about the status of your JFrog services and now includes monitoring for Pipelines.
Improved Artifactory Installation and Setup Using Oracle Database
When using an external Oracle DB as the Artifactory database, you no longer need to manually install and set up Liabio as it is now bundled into the Artifactory installer.
Database Performance Improvements in HA Environments
Reduced Database lock contention and Database loads in High Availability (HA) environments.
S3 Storage Direct Upload Mechanism
From Artifactory 7.9, you have the option to select the Direct Upload Mechanism which serves as an alternative to the existing default Eventual Upload mechanism, whereby the upload is not considered successful until it reaches the S3 storage.
Upgraded AWS SDK Bundled with Artifactory
Upgraded the AWS SDK bundled with Artifactory to support the use of service account IAM roles. AWS SDK v. 1.11.496 includes a feature for granting IAM roles to Kubernetes service accounts, instead of granting an IAM role to an EC2 machine, or using an open-source project.
Hazelcast is Deprecated
The write-locking method and UI session sharing between the JFrog Platform cluster nodes using Hazelcast is no longer supported. For more information, see the Support Blog.
Fixed an issue whereby, binding users in Artifactory using Google OAuth did not function correctly.
Fixed an issue whereby, Helm and Go users failed to create virtual repositories on Artifactory Edge nodes due to the inability to point to remote repositories on the Edge node.
Fixed an issue whereby, Support Bundles did not include logs.
Fixed an issue whereby, the
For a complete list of changes, please refer to our JIRA Release Notes.