Released: 10 January, 2022
Important Notice
When upgrading to Artifactory 7.31.10, Artifactory will fail to start up if the system property allowExternalConversionScripts is set to true and there is no External Conversion script provided.
As a workaround, remove the system property allowExternalConversionScripts or set it to false. For more information, see Known Issues.
This issue was resolved in the Artifactory 7.31.11 release.
Highlights
JFrog Projects Feature is Available to All JFrog Users
The JFrog Projects feature is now supported on all JFrog Subscriptions. JFrog Projects is a management entity for hosting your resources (repositories, builds, Release Bundles, and Pipelines), and for associating users/groups as members with specific entitlements. As such, using projects helps Platform Admins to offload part of their day-to-day management effort and to generate a better separation between the customer products to improve customer visibility on efficiency, scale, cost, and security. Projects simplify the onboarding process for new users, create better visibility for LOBs and project stakeholders. To learn more, see Projects.
Number of Projects Supported Per Subscription Type
All JFrog subscription types can create up to three projects in parallel to JFrog supporting extended usage of 30 projects for Enterprise subscriptions, and 300 projects for Enterprise+ subscriptions.
Pub Repository Support (Beta Version)
Artifactory now natively supports Dart packages, giving you full control of your deployment and resolution process of Flutter, Angular Dart, and general Dart programs. You can create secure and private local Pub repositories with fine-grained access control. Remote Pub repositories proxy remote Dart resources and cache downloaded Dart packages to keep you independent of the network and the remote resource, and virtual pub repositories give you a single URL through which to manage the resolution and deployment of all your Dart packages. To learn more, see Pub Repositories.
S3 with Storage Sharding Support
Artifactory introduces S3 Sharding template (s3-sharding) that utilizes a new sub-provider, state-aware-s3, so that you can use multiple S3 buckets with sharding as the Artifactory file store. For more information, see S3 Sharding.
High Availability in PostgreSQL Database
Artifactory introduces the ability to set up PostgreSQL databases in an HA configuration to be used as the Artifactory database. For more information, see PostgreSQL.
Feature Enhancements
Priority Resolution Supported on Federated Repositories
Added support for setting Priority Resolution on Federated repositories. Setting Priority Resolution takes precedence over the resolution order when resolving Federated repositories and will cause metadata to be merged only from repositories set with this field. If a package is not found in those repositories, Artifactory will merge metadata from the repositories that have not been set with the Priority Resolution field.
Garbage Collection Improvements
To improve Garbage Collection performance, you can now disable size-based ordering of the GC query. As a result, artifacts will not necessarily be deleted from largest to smallest. For more information, see Garbage Collection.
NuGet SetMeUp API v3 Enhancements
The NuGet package Set Me UP page in the JFrog Platform UI has been redesigned to reflect the best practices promoted by NuGet regarding the usage of API v3 over API v2. For more information, see Configuring NuGet Repositories.
Introducing npm SHA512 Support
From npm version 5, all npm packages published to Artifactory will support both SHA512 and SHA1 while using the strongest algorithm available, which will result in improved performance, robustness, and enhanced fault-tolerance. For more information, see v500.
Artifactory now supports SHA512 checksum when publishing to Artifactory with npm versions greater than 5 (containing sha512).
Checksum Policy Support for NPM Uploads
Added support for checksum validation on the NPM Tarballs when running the NPM Publish command.
Resolved Issues
JIRA Issue | Description |
|---|---|
Fixed an issue whereby, deployed Helm charts in the virtual Helm repository index could not be found. | |
Fixed an issue whereby, Artifactory prompted for a username and password when accessing a file link in the Native Browser. | |
Fixed an issue whereby, builds containing slashes in the name, returned a 404 error message in the UI when using an Apache reverse proxy. | |
Fixed an issue whereby, the download counter was increased when clicking the PyPI Info tab. | |
Fixed an issue, whereby Artifactory could not be used as a BuildKit remote cache. | |
Fixed an issue, whereby a user with Delete Release Bundle permissions in the Edge node was not able to delete a Release Bundle version. | |
Fixed the issue, whereby the logging system got stuck on Windows machines | |
Fixed an issue whereby, retrieving NuGet packages, caused Artifactory to return a 404 error message if the uploaded package contained uppercase letters and the request contained only lowercase characters. | |
Fixed a bug whereby, using specific prefixes( | |
Fixed an issue whereby, a paginated Docker catalog call was slow due to an exclusion pattern. | |
Fixed an issue whereby, Artifactory stopped working if the first shard in a sharding environment was unavailable. | |
Fixed an issue whereby, performance slowness was detected, during bursts of anonymous requests, due to the ineffectiveness of the RateLimit external library. | |
Fixed an issue whereby, illegal characters in build names caused builds to crash without generating an error message. | |
Fixed an issue whereby, RPM repository type packages were not saved as YUM files. | |
Fixed an issue whereby, the upgrade process failed if no JFrog license was found. Note: Applies only to Enterprise+ subscriptions | |
Fixed an issue whereby, empty repositories were getting listed even if the repository didn't allow anonymous access. | |
Fixed an issue whereby, Artifactory did not resolve | |
Fixed an issue whereby, when working with Projects, Project Admins could list all the repositories including those that users could not access. | |
Distribution removes the properties that were set on the edge node repository. This means that there is a possibility that all the properties set by the customer will be overridden. While this affects Distribution, the fix was in Artifactory. | |
Fixed an issue whereby, the ' | |
Fixed an issue whereby, Project Admin could list repository names to users without the relevant permissions. | |
Fixed an issue whereby, the repositories were not displayed in the Storage Summary page in the UI. | |
Fixed an issue whereby, HA licenses were displayed incorrectly as Standalone instances in the Licenses page in the UI. | |
Fixed an issue whereby, the Build Status page in the UI referred to artifacts from different repositories, and not from that repository that was used to promote the build. |