Issue
-
After upgrading the artifactory plugin from 3.4.1 or earlier to a version earlier than 3.7.2, the global Artifactory server credentials configuration under is lost.
Environment
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
-
CloudBees CI (CloudBees Core) on modern cloud platforms - Operations Center
-
CloudBees CI (CloudBees Core) on traditional platforms - Client controller
-
CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
-
CloudBees Jenkins Enterprise - Managed controller
-
CloudBees Jenkins Enterprise - Operations center
-
Artifactory plugin from version 3.5.0 to 3.7.2 excluded
Related Issues
-
artifactory #299: Global Artifactory Server configuration lost when upgrading from 3.4.1
Explanation
In version 3.5.0 of the Artifactory plugin, a credential converter was introduced to provide backward compatibility with recent changes made to the type of stored credentials in the Artifactory Server configuration. However a bug in this converter causes the credentials configuration to not be readable anymore by Jenkins when the component is loaded, and report the problem in .
When in that state, **if an administrator saves the Jenkins global configuration the erroneous artifactory server configuration will be persisted, which could cause builds relying on this configuration to fail.
See the full details in [artifactory #299](https://github.com/jfrog/jenkins-artifactory-plugin/issues/299