|
||||||||
|
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/d/optout.

I have the same issue, yes I looked at issue #21785 - but I do have valid credentials for my externals, which all use exactly the same authentication realm as the rest of my subversion repository (I validated every single one of them) - which works fine for the main repo and for some other externals.
I have to add the followint things:
Adding identical 'additional credentials' seems to work - but is a bit silly, not to mention a massive job to filter though all 250 active jobs we have that happen to use externals, and I'm not blindly going to add additional credentials to every single job using groovy script (which would also take a good while to figure out how exactly, I'm not that familiar with it) for something that should be fixed in the future - requiring some massive cleanup which would be even more complex than now filtering through all those jobs.
I'm running Jenkins ver. 1.577 with SVN plugin ver. 2.4.3.