On Tuesday, April 16, 2024 at 5:36:58 AM UTC-7 you wrote:
Hi, we are currently transforming all our SCMs to git. That worked for the jobs that rely on a global library and just have a function-call in the pipeline that's directly set in the job configuration. However I have a couple of auxiliary jobs that are configured as 'Pipeline script from git' Here I am experiencing some problems I am not used to from the old SCM: - the selection 'credentials' is empty even though there are a couple of credentials in and escpecially one I use from a 'checkout' step from my library - when I add new credentials with the button 'add' one line below the selection still does not show anything. - the newly added credentials are shown in the global credentials administration list and I am not allowed it another time Is there a known bug in this area or is there something I am doing wrong? You are probably seeing a limitation of the git plugin. It accepts ssh private key credentials for git connections over ssh (either ssh:// or git@hostname:) and it accepts username / password credentials for git connections over HTTP (either http:// or https://). If your credential is a secret text or some other form of credential, the git plugin won't show it in the dropdown list because it only supports those two types of credentials. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/af180528-7f4d-4ccc-b9e7-750d91e63c4fn%40googlegroups.com.
