|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The scenario as described shouldn't be possible, and I can only reproduce this if I create a job before any credentials have been created.
Adding more credentials to Jenkins won't cause the "googleCredentialsId" to be set in any job, unless the job configuration page is opened, and then the Save button is clicked.
But it's a known issue that the error messages relating to credentials can be improved, and the plugin should also be able to handle renaming of credentials, as currently renaming credentials after a job has been configured causes the above stacktrace.