Artifactory 7.80.0 Cloud

Released: 14 February, 2024

Feature Enhancements

Support for new CocoaPods CLI Commands
Artifactory now supports using the pod search and pod list commands for local and remote CDN repositories.
Auto Healing of Federated repositories enabled by default
The auto-healing mechanism introduced in version 7.71.1 is now permanently enabled for all customers who work with Federated repositories. This mechanism checks Federated repositories at regular intervals for exhausted queues (queues that have exceeded the maximum number of attempts to send events to other Federation members), resets the failed events automatically, and tries again to sync with the target mirror. For more information, see Federation Recovery and Auto-Healing.Federation Recovery and Auto-Healing
Solutions for resolving 'stuck' Full Sync operations on Federated repositories
Two new options have been introduced for resolving Full Sync operations that have become 'stuck', meaning the operation persists in the database but is not active in memory. For example, this situation can arise if a user restarts an Artifactory instance while a Full Sync operation is in progress.
1. A new async task defined in the system.properties file (artifactory.reset.stale.full.sync.job.interval.min) can reset the status of a Full Sync operation that has become 'stuck', enabling the operation to restart.Federation Recovery and Auto-Healing
2. A new Force Full Sync API enables you to force a Full Sync operation between the Federated repository members, interrupting another Full Sync operation that is already in progress.Federated Repository Force Full Sync
New menu options for creating Release Bundle v2 versions
The Actions menu in the Release Lifecycle Management kanban board now includes options for creating a new version of the selected Release Bundle v2 from builds or other Release Bundles. For more information, see Create a New Version of an Existing Release Bundle.
Helm Virtual index.yaml Resolution Improvements
We have improved our index calculation mechanism for virtual repositories to minimize potential OOM issues. We recommend setting the Metadata Retrieval Cache Period (Sec) in the repository page in the JFrog Platform WebUI to 60 seconds or more. For more information, see Helm Virtual Repository Index Improvements.
Automatically pair OAuth SSO users with JFrog Platform users
You can now automatically pair OAuth SSO users when they log in to the JFrog Platform with their JFrog Platform user based on their email address. No configuration change is required to enable the feature. For more information on OAuth SSO, see OAuth SSO.OAuth SSO

Resolved Issues

JIRA Issue	Severity	Description
RTFACT-30253	Medium	Fixed an issue whereby, when enabling the “Disable Artifact Resolution in Repository“ setting at the repository level, it was still possible to download the entire repository’s content as a ZIP file.
RTFACT-30243	Medium	Fixed an issue related to RPM whereby, when deploying a package with a name containing the substring `_tmp_`, Artifactory did not index it as expected.
RTFACT-30272	Low	Fixed an issue related to Maven whereby, when deploying a snapshot to a local repository with the `artifactory.maven.authentication.nonPreemptive` property enabled, Artifactory did not perform as expected.
RTFACT-30256	Low	Fixed an issue related to P2 whereby, Artifactory did not support creating a Smart Remote repository with a key containing special characters.
RTFACT-30208	Low	Fixed an issue whereby, when running the Update Repository Configuration REST API using a mismatched `rclass` parameter, Artifactory returned a 400 error specifying the `rclass` always as ‘local’, regardless of the repository type.
RTDEV-39093	Critical	Fixed an issue that excluded certain properties by default (`build.name`, `build.number`, `build.timestamp`) when promoting a Release Bundle v2 version.
RTDEV-39037	Critical	Fixed an issue that prevented a Release Bundle v2 from collecting all artifacts of the same name from within a single build-info module.
RTDEV-38945	Medium	Fixed an issue whereby, Xray did not support scanning builds with names containing German umlaut characters (ü).
RTDEV-38928	Medium	Fixed an issue that caused errors in the Release Lifecycle dashboard due to Release Bundle v2 promotions to a renamed or deleted environment.
RTDEV-38927	Medium	Fixed an issue that prevented failed Release Bundle v2 promotions from appearing with the correct icon on the Release Lifecycle dashboard.
RTDEV-38828	Medium	Fixed an issue whereby the process of reading the same binary multiple times simultaneously to the Cached Filesystem Binary Provider was getting stuck and caused high CPU processing.
RTDEV-37966	Medium	Established a limit to the number of versions (default = 200) that can be displayed for one Release Bundle v2 on the Release Lifecycle dashboard.
RTDEV-37678	Medium	Fixed an issue that caused the promotion and distribution filters on the Release Lifecycle dashboard to present Release Bundle versions created during the selected timeframe instead of versions that were promoted or distributed during that timeframe.