It's possible to go through creation using the Git + SSH flow but the created MBP will fail to index due to public key failure.

It appears there is a case where a "BlueOcean Folder Credential" is being used / created with the same ID as the auto-generated user private SSH key, for example an instance that exhibited this issue had: blueocean-folder-credential-domain with this id: jenkins-generated-ssh-key and was showing "BlueOcean Folder Credential" in the MBP config. Presumably the Git plugin doesn't know how to deal with this non-SSH credential as an SSH key. Need to make sure this can't happen...