|
||||||||
|
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.
As I said in the PR 14, this is not this simple
The last time I looked at it, I was stuck on some svn/git differences in behaviour (having to rely on a generic layer for SCM manipulations is not always obvious).
This makes me wondering if current issue is "fixable" given the current state of the project.
It might be handled if I was dropping the use of scm API (that is to say, reimplement only my needed commands) and use jenkins' own credential api (see JENKINS-18129)