jenkinsci / jenkinsci/subversion-plugin

[JENKINS-29898] Allow subversion post-commit hook handler to work with svnlook dirs-changed (not just svnlook changed)

Open
#1,294 0 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

My subversion server administrator set up a post-commit script for me, but changed the "svnlook changed" command to "svnlook dirs-changed".

From the Jenkins logs, I can see that the first four characters are stripped off of each path name, I guess to remove the "U " status info that "svnlook changed" sends. (In the log, I see that "my-project/trunk" comes through as "roject/trunk".)

It'd be nice if the plugin could be adapted to accept the format without the status component – for us, simply knowing a change went into a given branch is sufficient to warrant kicking off a build.

---
Originally reported by jladan, imported from: Allow subversion post-commit hook handler to work with svnlook dirs-changed (not just svnlook changed)


  • status: Open
  • priority: Minor
  • component(s): subversion-plugin
  • label(s): subversion, trigger
  • resolution: Unresolved
  • votes: 0
  • watchers: 2
  • imported: 20251212-090250

Raw content of original issue

My subversion server administrator set up a post-commit script for me, but changed the "svnlook changed" command to "svnlook dirs-changed".

From the Jenkins logs, I can see that the first four characters are stripped off of each path name, I guess to remove the "U " status info that "svnlook changed" sends. (In the log, I see that "my-project/trunk" comes through as "roject/trunk".)

It'd be nice if the plugin could be adapted to accept the format without the status component – for us, simply knowing a change went into a given branch is sufficient to warrant kicking off a build.

  • environment: Jenkins ver. 1.609.2, Subversion plugin 2.5.1.

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.