-
Improvement
-
Resolution: Won't Fix
-
Major
-
non OS dependent
currently jenkins configuration files are synched directly to the root directory of a repository, which is creating quite a mess having all of them at the same level with other sources in one single repo.
It should be possible to define e.g. the relative path inside the repo where the configuration is synched to.
This configuration should be done when configuring the plugin.
focus should be on git (if separate implementation is necessary)
[JENKINS-20626] SCM-sync-configuration plugin: make root directory in repository configurable
Sven Keller
created issue -
| Workflow | Original: JNJira [ 152151 ] | New: JNJira + In-Review [ 178198 ] |
Frédéric Camblor
made changes -
| Assignee | Original: Frédéric Camblor [ fcamblor ] | New: Craig Rodrigues [ rodrigc ] |
Craig Rodrigues
made changes -
| Assignee | Original: Craig Rodrigues [ rodrigc ] |
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.
| Resolution | New: Won't Fix [ 2 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
I don't think separate implementation for each SCM is necessary.
Providing a new relative path at scm-sync-configuration config section (which then could be used in ScmSyncConfigBusiness. getCheckoutScmDirectoryAbsolutePath()) would be sufficient.