jenkinsci / jenkinsci/subversion-plugin

[JENKINS-45070] Change list not populated when checkout via Multiple SCM plugin

Open
#1,428 1 comment 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

When a SVN repository is checkedout using the Multiple SCM changes, the Jenkins build page does not list any changes, even though there are commits.

However, when an SVN repository is checkout using the normal "Subversion" plugin, the list of commits are displayed on the job build number page.

 

The slave does not have SVN cli tools installed, but the subversion client is

```
TortoiseSVN 1.7.13, Build 24257 - 64 Bit , 2013/06/01 07:32:54
Subversion 1.7.10,
apr 1.4.6
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.1e 11 Feb 2013
zlib 1.2.7
```

 

---
Originally reported by bassam_khouri, imported from: Change list not populated when checkout via Multiple SCM plugin


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

Raw content of original issue

When a SVN repository is checkedout using the Multiple SCM changes, the Jenkins build page does not list any changes, even though there are commits.

However, when an SVN repository is checkout using the normal "Subversion" plugin, the list of commits are displayed on the job build number page.

 

The slave does not have SVN cli tools installed, but the subversion client is



TortoiseSVN 1.7.13, Build 24257 - 64 Bit , 2013/06/01 07:32:54

Subversion 1.7.10,
apr 1.4.6
apr-utils 1.3.12
neon 0.29.6
OpenSSL 1.0.1e 11 Feb 2013
zlib 1.2.7


 

environment

```
- Jenkins master OS: Windows Server 2012 R2 (x86)

- Jenkins version: 2.46.3

- Multiple SCM plugin version: 0.6

- Subversion plugin version: 2.7.1

- Jenkins is being run directly and was installed via Windows Installer

- The Windows slaves are primarily launched via JNLP. The slave agent may be running as a service.
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.