![]() |
|
|
|
|
Change By:
|
Frédéric Camblor
(29/May/13 12:16 PM)
|
|
Description:
|
As discussed in JENKINS-18124 by ndeloof & stephenconnolly, we might improve scm authentication by using
[
credentials-plugin
|https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin]
instead of maven-scm-provider's APIs.
If done, we could wonder if it wouldn't be interesting to get rid of maven-scm-api abstraction and, instead, use some NIH to bring our own abstraction layer for scm manipulations dealt by the plugin.
I'm not really satisfied with maven-scm-api for 2 reasons :
- Some generic abstractions differ in their implementation (for instance, update() will not act the same with DVCS and VCS scms : svn will update current working copy whereas git will not *always* do a fetch)
- Some implementations are not generic because not generalized yet amongst every SCMs (for instance, the log() command, accessible in SVN, is not generically available)
ATM, we're only relying on a subset of available generic methods (see [SCMManipulator class|https://github.com/jenkinsci/scm-sync-configuration-plugin/blob/master/src/main/java/hudson/plugins/scm_sync_configuration/SCMManipulator.java] which represents the SCM access layer)
|
|
|
|
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.
