jenkinsci / jenkinsci/subversion-plugin

[JENKINS-28749] Incorrect local modification being identified when svn:keywords are used on 1.8

Open
#1,273 4 comments 0 reactions 0 assignees View on GitHub
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

We have just upgraded jenkins from using 1.5 subversion clients to using 1.8

When jenkins checks out a project that has files using svn:keywords it is incorrectly identifying local changes. The revision number in the file is being indicated as the n-1 time the file was physically changed and not the last time.

When the project is checked out using command line svn 1.8.13 the files are checked out correctly with no local changes, so there appears to be a difference between jenkins svn and installed svn.

---
Originally reported by dan_smartstream, imported from: Incorrect local modification being identified when svn:keywords are used on 1.8


  • assignee: recena
  • status: Open
  • priority: Minor
  • component(s): subversion-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 3
  • imported: 20251212-090250

Raw content of original issue

We have just upgraded jenkins from using 1.5 subversion clients to using 1.8

When jenkins checks out a project that has files using svn:keywords it is incorrectly identifying local changes. The revision number in the file is being indicated as the n-1 time the file was physically changed and not the last time.

When the project is checked out using command line svn 1.8.13 the files are checked out correctly with no local changes, so there appears to be a difference between jenkins svn and installed svn.


environment

```
jenkins 1.583

subversion-plugin 2.5
```

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.