We have created a Perforce credential on our Cloudbees Core CI instance which is being propagated to all its child Jenkins masters. After our update of Cloudbees Core, the Jenkins credential plugin was updated to version 1189.vf61b_a_5e2f62e, and with this the P4 credentials now are not being propagated correctly, with their true type

Before the update, the P4 credential was seen on both our Operations center, and all children Jenkins masters as type: org.jenkinsci.plugins.p4.credentials.P4PasswordImpl

After the update, the type of the credential propagated to masters has changed on the level of the masters to become:

com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl

We have raised this our provider Cloudbees and following was their response:

"We have confirmed that the problem is coming from a change introduced in the credentials plugin. Perforce plugin might need to include a fix to address the change. The Perforce plugin requires a very old version of the credentials plugin which is not compatible with the one included in the last release.

The problem seems to be coming because the credential should be snapshoted (self-contained and not referring to any external stores). The implementation seems to be broken in the perforce plugin for this new version of the credentials plugin."

As we can see, it seems the P4 plugin is not inline with a new change on the level of the Credentials plugin on Jenkins, and it needs adaptation in order to have its credentials type shown correctly