Artifactory 7.11.1 Cloud

Released: 17 November, 2020

Artifactory 7.11.1 is Available as a Cloud Version

The JFrog Artifactory 7.11.1 release is available as a Cloud version and is aligned with the Artifactory7.11.2 Self-Hosted version.

Highlights

Helm V3 Support

Artifactory now supports Helm 3 clients, enabling you to deploy and resolve Helm Charts using Helm V2 and V3 clients.

OCI Support

Artifactory is now OCI-compliant and supports OCI clients, providing you with the ability to deploy and resolve OCI images in Docker Registries.

Note

The OCI client Singularity is not supported.

Live System Logs

You can now view or download essential Platform system log files for each of JFrog's services; Artifactory, Xray, Mission Control, and Pipelines. For more information, see Viewing Log Files from the UI .Logging

Feature Enhancements

Improvements to RubyGems Indexing for Local Repositories

Added Bundler Compact index support for Local repositories, in addition to the Remote repositories, providing you with the latest version of the package that is compatible with your installed Ruby version of the project.

To use this new capability, in the artifactory.system.properties file, set the artifactory.gems.compact.index.enabled=true value.

PostgreSQL Database Improvements

Introduced the following improvements:

PostgreSQL database indexing improvements

Indexing on bundle_files for delete operations

Resolved Issues

Jira Issue	Description
RTFACT-23808	Fixed an issue, whereby under certain circumstances, running Event-based Pull Replication on many files may have caused Artifactory to crash.
RTFACT-22944	Fixed an issue, whereby searching for Nuget packages using the Tag or PackageId did not work outside of `Nuget.Org.`
RTFACT-15320	Fixed an issue, whereby you could not run a single node to process `*-delete` files of the `eventual _queue` folder on each node of an HA cluster when the cluster-s3 template is used for the `binarystore.xml`.
RTFACT-19479	Fixed an issue, whereby multiple delete events were processed on multiple nodes that led to multiple delete requests for the same resource storing on the Cloud instance. After the fix, only single node processes delete requests.
RTFACT-22366	Fixed an issue, whereby Artifactory returned the PyPi yanked release as the latest version.
RTFACT-17273	Fixed an issue, whereby pulling and pushing the same Docker image simultaneously, returned an “unknown blob” error.
RTFACT-18471	Fixed an issue, whereby empty virtual repositories were not listed when running the Get Repositories REST API.
RTFACT-23864	Fixed an issue, whereby running the `POST /ui/userProfile` REST command will no longer require a password for performing CROWD actions.
RTFACT-20610	Fixed an issue, whereby deleting a Debian repository after copying the contents to a different Debian repository displayed `N/A repository/package type` in the Storage Summary log.
RTFACT-23318	Fixed an issue, whereby in an HA environment, system export did not export repositories when running on members.
RTFACT-15797	Fixed an issue, whereby users could not name the NPM local repository as `npm`.
RTFACT-23665	Fixed an issue, whereby a Docker remote repository did not trigger the `beforeRemoteDownload` plugin execution point.
RTFACT-23307	Fixed an issue, whereby the apt-get client failed when the Debian repository was configured with CDN.
RTFACT-23764	Fixed an issue, whereby Artifactory was losing track of the `cacheFS` data size on the disk, after an upgrade and a restart. Once Artifactory lost track of the `cacheFS` size, it reset the amount of space used to zero bytes.
RTFACT-23816	Fixed an issue, whereby a DataSource memory leak occurred when using MySQL.
RTFACT-9208	Fixed an issue, whereby we now provide release fields content for Debian repositories.
RTFACT-23651	Fixed an issue, whereby the `Label` attribute in a Debian Release file was set to the repository name instead of the hardcoded `Artifactory`.
RTFACT-23275	Fixed an issue, whereby the performance of the `distributed_locks` table in PostgreSQL was improved.
	Fixed an issue, whereby Access Federation issues were arising between servers of different versions, where the source version was higher than the target version.
	Fixed a `join.key` bootstrapping issue, whereby the system would not accept the user-provided join.key if an existing join.key was already registered.

For a complete list of changes, please refer to our JIRA Release Notes.