jenkinsci / jenkinsci/subversion-plugin

[JENKINS-15135] Support for "Poll on Master" for Subversion SCM plugin

Open
#966 2 comments 0 reactions 0 assignees View on GitHub
component:subversion-plugin imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
131
Forks
275
Avg merge
12h 4m
Merged PRs (30d)
6

Description

When slaves aren't always available sometimes the workspace goes missing - in this case, all affected task (i.e. those on the master) get rescheduled for building when their SCM is checked for a later revision.

Polling on Master (see Perforce plugin) would address this issue, and remove excessive rebuilds. As we've got a massive amount of idle jobs active this hits us hard every time a slave goes offline (for any reason), or when Jenkins is restarted (for any reason), and doesn't know its slaves yet.

I'm willing to write the actual patch, but would need some advice on how to add that to the code in a manner consistent with the current ideas behind it (there seems to be some code in place already, but it's not connected to the config interface or seemingly doing very much).

---
Originally reported by berlincount, imported from: Support for "Poll on Master" for Subversion SCM plugin


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

Raw content of original issue

When slaves aren't always available sometimes the workspace goes missing - in this case, all affected task (i.e. those on the master) get rescheduled for building when their SCM is checked for a later revision.

Polling on Master (see Perforce plugin) would address this issue, and remove excessive rebuilds. As we've got a massive amount of idle jobs active this hits us hard every time a slave goes offline (for any reason), or when Jenkins is restarted (for any reason), and doesn't know its slaves yet.

I'm willing to write the actual patch, but would need some advice on how to add that to the code in a manner consistent with the current ideas behind it (there seems to be some code in place already, but it's not connected to the config interface or seemingly doing very much).

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.