jenkinsci / jenkinsci/subversion-plugin
[JENKINS-9147] Access problem to SVN server is handled as scm change, but restoring connection is not
- Dominant language
- Java
- Stars
- 131
- Forks
- 275
- Avg merge
- 12h 4m
- Merged PRs (30d)
- 6
Description
We have projects that are triggered by SCM changes. We've noticed that if there is a network failure or server maintenance (connection to SVN server can't be made), situation is handled as SVN change and project is triggered and of course failed.
When SVN server is back on-line, projects are not triggered automatically, since technically, there is no changes. This results all SCM-triggered projects show as failed until they are triggered manually -or new commits are made.
---
Originally reported by swiksted, imported from: Access problem to SVN server is handled as scm change, but restoring connection is not
Raw content of original issue
We have projects that are triggered by SCM changes. We've noticed that if there is a network failure or server maintenance (connection to SVN server can't be made), situation is handled as SVN change and project is triggered
and of coursefailed.When SVN server is back on-line, projects are not triggered automatically, since technically, there is no changes. This results all SCM-triggered projects show as failed until they are triggered manually -or new commits are made.
- environment:
Ubuntu 10.4 (LTS) (64bit)
Contributor guide
Assessment
This issue has not been assessed yet.