|
||||||||||||||
|
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.
I resolved my issue.
I had a couple of issues that culminated in the authentication exception:
1) The credential ID in credentials.xml did not match the one Jenkins was trying to use. I resolved this by configuring the slave node and just hitting save. This refreshed the ID
2) I am confused about this resolution, but the private key credential was previously using the user@slave's private key directly entered. This was invalid as it should be jenkin@master's private key. Somehow, the former input was working prior to update.