|
||||||||
|
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.
We've the same issue with v1.594, however, if the plugin gets a downgrade to 2.4.5 I get authentication broken in the job per SCM in MultiSCM with Subversion configuration.
I guess the workaround to this is to set global credentials and use that as new credential settings for 2.4.5?
Michael Shmulevich, does your proposed workaround works with 2.5 as well (asking because you mentioned „Download any version [...]”)?