|
||||||||
|
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/groups/opt_out.
... you get this (FailedWorkaround2).
This issue causes immense problems as our whole CI environment for all our builds depend on it.
So, for us it is not only critical - it is nearly a blocker!
I tried another workaround by using a text field parameter where the particular branch or tag can be typed in instead of choosing from a list.![]()
)
But I failed getting the same error message!
(Not very suprprising as this parameter type does not care about Subversion.
It seems like the provided parameter setting of the plugin does not conform to the new credentials framework where you can choose from a list of saved credentials.
But: The main part of the plugin that can be found in the section "Source Code Management" does that now.
Hence, it seems like an inconsistency.
It would be highly appreciated if this bug would be fixed soon according to the mentioned situation.