Released: 30 September, 2021
Artifactory 7.27.3 is Available as a Cloud Version
Artifactory 7.27.3 release is available only as a Cloud version.
As described in the Known Issues page, the
Delete From Archive feature on a Cold Artifact Storage retention policy may have cleaned archived artifacts prematurely due to an issue described in RTFACT-26491. Therefore, we recommend to disable the
Delete From Archive option in this release.
This issue has been resolved in Artifactory version 7.27.10.
Announcing JFrog Artifactory Cold Artifact Storage Feature
The JFrog Cold Artifact Storage enables organizations to save cost and improve usability and performance by providing the ability to retain unused artifacts that cannot be deleted for several years due to regulatory obligations. Cold Artifact Storage enables you to move these artifacts from one Artifactory instance to another Artifactory instance that is connected to cost-effective storage. Artifacts that are moved to the Cold instance are removed from the Live Artifactory instance, thereby reducing the number of artifacts that require maintenance, which helps to improve the usability, search capabilities, and performance of the Live instance. For more information, see Cold Artifact Storage.
JFrog Cold Artifact Storage is available only as an on-prem feature.
Currently there is a limitation when using cold storage with a federated repository. If a retention policy (used to archive artifacts or packages to a cold storage server) is configured to clear artifacts or packages from a federated repository, the archiving event and any restore event will not be synced with the federation members. In addition, any deleted artifacts or packages will be recreated due to the federation. Therefore, it is not recommended to use cold storage with federated repositories.
In a future version, the sync with the federation members will be enabled.
PHP Composer Virtual Repositories
As part of our initiative to support PHP Composer versions 1 and 2 and support for downloading Drupal file versions 7 and 8 from remote repositories, we now support PHP Composer virtual repositories version 2 (version 1 is not supported). A virtual repository is a collection of local, remote, and other virtual repositories accessed through a single logical URL. It hides the access details of the underlying repositories letting users work with a single, well-known URL. The underlying participating repositories and their access rules may be changed without requiring any client-side changes. For more information, see PHP Composer Virtual Repositories.
JFrog Mission Control is Now Integrated as a Service in Artifactory
From this version, Mission Control is now a dedicated service in Artifactory and manages the connectivity between the Platform Deployment units. The dashboard and metrics are now part of a new dedicated product called Insight. For more information, see Migrating Platform Deployments and License Buckets.
Extended the Priority Resolution feature to Support PHP Composer Repositories
You can now declare local and remote repositories as ‘safe’ by enabling the ‘Priority Resolution’ field for Localand Remote repositories for PHP Composer packages.
HELM Remote Repositories Improvements in the UI
Helm Charts requested by the Helm client frequently use external dependencies as defined in the
index.yaml file. These dependencies may, in turn, need additional dependencies. Therefore, when downloading a chart, you may not have full visibility into the full set of dependencies that your original chart needs (whether directly or transitively). As a result, you are at risk of downloading malicious dependencies from unknown external resources.
To manage this risk, and maintain the best practice of consuming external charts through Artifactory, you may specify a "safe" Allow List from which dependencies may be downloaded, cached in Artifactory, and configured to rewrite the dependencies so that the Helm client accesses dependencies through a remote repository. For more information, see Automatically Rewriting External Dependencies.
Increased the number of characters supported for a Project key up to 10 chars.
Added the ability to share repositories within a Project/s in Read-Only mode to avoid any changes or modifications of the shared content.
Docker Push Image Performance Improvements
Improved speed when pushing new Docker images to Docker repositories by implementing enhancements to the internal Docker Blob Search mechanism.
Expanded Indexing to Support .ddeb Files for Debian Repositories
Added support for Indexing debug symbols for Debian repositories. For more information, see Debian Repositories.
Enhanced the Get Reverse Proxy Configuration REST API Permissions
Users running the Get Reverse Proxy Configuration REST API can now view proxy information based on their permission set.
Fixed an issue whereby, the
Fixed an issue, whereby Cargo reindexing was not functioning in Windows environments.
Fixed an issue whereby, Amazon content browsing was regarded as an XML, even if the returned content type was an HTML.
Fixed an issue whereby, when installing Nuget packages with multiple source authors, to a remote Nuget repository pointing to a Proget v3 feed, caused Artifactory to fail and return a 500 internal server error.
Fixed an issue whereby, choosing to change the default proxy, would override all remotes with no proxy or the previous default proxy, and added an option to change the proxy without affecting current ones.
Fixed an issue whereby, the SHA256 migration job failed with errors due to missing SQL conversion files on Artifactory 7.23.3.
Fixed an issue whereby, under certain circumstances, 7Z files could not be expanded a folder in the tree view of Artifactory.
Fixed an issue whereby, running an incorrect block error was generated for a failed Docker Pull, if Xray was unavailable.
Fixed an issue whereby, if Content Browsing is enabled on the repository, clicking on the