|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I also encounter this issue, on a Debian machine in my case.
The strange thing is that if, after such a "No credential to try" failure, the next (manually started) build always seems to run fine.
I have not listed all externals as separate 'modules' in my job configuration, but I have configured additional credentials for the realm to which all externals belong.