|
||||||||
|
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.
@Nicolas I agree with you on the fact that only a little set of maven-scm is used.
And relying on it shows its limits as soon as a feature is not "generically" available for every scms (see JENKINS-14841).
So your proposal makes sense.
What I'm not confident about this proposal is the way authentication will be handled on SCM. Is Jenkins SCM API providing generic way to authenticate against stored credentials in jenkins ?
If it would be the case, it would be great !
@Henri Dependency against core is the burden of every plugin maintainers.![]()
But I don't know there is a better way to handle this.
This was the intention of the plugin-compat-tester .. but I didn't have enough time recently to improve it