jenkinsci / jenkinsci/subversion-plugin

[JENKINS-54025] Similar issues seen with P4 plugin also seen with Subversion plugin regarding triggered builds

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

Description

Here is a list of P4 plugin issues that I'm also seeing with the Subversion plugin:

 




JENKINS-53922">JENKINS-53922
Poll results in changes always found when using 2 global libraries



JENKINS-44358">JENKINS-44358
the first time scm polling of a job after server restart always return "changes found"

We run nightly builds if there are changes in Subversion to items in the include list (we also use the exclude list). After we restart the Jenkins host, some projects will run a nightly build and list no changes in the change list even though it says there was a change.

Also, we will see a nightly build that failed be triggered the next night and list no changes in the change list. So, no reason to trigger it, but it is triggered anyway. It will keep on failing every night until I get it to succeed at which point it will not be triggered the next night.

---
Originally reported by kerrhome, imported from: Similar issues seen with P4 plugin also seen with Subversion plugin regarding triggered builds


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

Raw content of original issue

Here is a list of P4 plugin issues that I'm also seeing with the Subversion plugin:

 




JENKINS-53922
Poll results in changes always found when using 2 global libraries



JENKINS-44358
the first time scm polling of a job after server restart always return "changes found"

We run nightly builds if there are changes in Subversion to items in the include list (we also use the exclude list). After we restart the Jenkins host, some projects will run a nightly build and list no changes in the change list even though it says there was a change.

Also, we will see a nightly build that failed be triggered the next night and list no changes in the change list. So, no reason to trigger it, but it is triggered anyway. It will keep on failing every night until I get it to succeed at which point it will not be triggered the next night.

  • environment: Jenkins LTS 2.138.1, Subversion 2.11.1 thru 2.12.1 (at least, but I think some of these issues I'v seen with earlier versions)

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.