[JENKINS-20450] svn::externals work improperly inside MultipleSCMs

Open

#1,080 opened on Nov 6, 2013 0 comments 0 reactions 0 assignees View on GitHub

component:multiple-scms-plugin component:subversion-plugin imported-jira-issue priority:minor resolution:unresolved

Dominant language: Java
Stars: 131
Forks: 275
Avg merge: 12h 4m
Merged PRs (30d): 6

Description

MultipleSCMs plugin allows to define multiple instances of SVN

SVN plugin is designed for only one instantiation in project => multiple SCMs lead to unpredictaable behavior

Example: Subversion plugin uses only one svnexternals.txt file per project

Workaround: define repositories inside a single SVN instance in MultipleSCMs

---
Originally reported by oleg_nenashev, imported from: svn::externals work improperly inside MultipleSCMs

assignee: kbell
status: Open
priority: Minor
component(s): multiple-scms-plugin, subversion-plugin
resolution: Unresolved
votes: 0
watchers: 2
imported: 20251212-090250

Raw content of original issue

MultipleSCMs plugin allows to define multiple instances of SVN

SVN plugin is designed for only one instantiation in project => multiple SCMs lead to unpredictaable behavior

Example: Subversion plugin uses only one svnexternals.txt file per project

Workaround: define repositories inside a single SVN instance in MultipleSCMs

environment: subversion-1.53

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

[JENKINS-20450] svn::externals work improperly inside MultipleSCMs

Description

Contributor guide

Assessment

Get new issues in your inbox