-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
As discussed in JENKINS-18124 by ndeloof & stephenconnolly, we might improve scm authentication by using 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 which represents the SCM access layer)
- is blocking
-
JENKINS-15128 Renaming job doesn't work with Git
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JENKINS-8527 Two way synchronization
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-18129] Using credentials-plugin to authenticate against SCMs & getting rid of maven-scm-api
Alec Matschiner
added a comment - I'm having the same issue that Nick Maynard is having. I'm unable to access the underlying file system of Jenkins so this makes it impossible to provide the correct SSH keys and OS-level credentials. So implementing the credentials plugin would be greatly appreciated!
Alec Matschiner
added a comment - I'm having the same issue that Nick Maynard is having. I'm unable to access the underlying file system of Jenkins so this makes it impossible to provide the correct SSH keys and OS-level credentials. So implementing the credentials plugin would be greatly appreciated! The scm sync configuration plugin is deprecated. No further work is expected on the plugin.
Users of this plugin are encouraged to migrate their jobs to Pipeline Plugin, so that their jobs will be specified in pipeline code that can be checked into an SCM, all without using the SCM Sync configuration plugin.
Users of this plugin are also encouraged to use the Configuration as Code Plugin to specify the configuration of their Jenkins server in a file which can be checked into an SCM, all without using the SCM Sync configuration plugin.
We work on a hosted Jenkins system in which we have no access to the underlying filesystem or config. We cannot update OS-level Git credentials - and so the SCM sync plugin simply doesn't work. Bringing it in line with the usual Jenkins SCM configuration would allow us to specify keys, etc. in Jenkins config... and everything would Work.