-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows, Visual SVN
After upgrade of Jenkins/Subversion plugin from version 1.447/1.39 to version 1.501/1.45, we have noticed significant delay in triggering builds on commit (around 1 minute). We are using notify CI method in our post-commit hooks.Users who do not have jobs configured in Jenkins are being badly impacted, while post commit hook notifies Jenkins.
Downgrading Subversion plugin back to 1.39 removes this issue, but we would like to be on a higher version as Subversion 1.7 is supported those versions.
- is duplicated by
-
JENKINS-17808 notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'
-
- Reopened
-
[JENKINS-17616] Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Link | New: This issue is duplicated by JENKINS-17808 [ JENKINS-17808 ] |
Attachment | New: exception_long_after_timeout.txt [ 23772 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Comment |
[ This bug is reproducible in the Jenkins version 1.633, with Subversion Plug-in 2.5.3 (pinned). The error in the post-commit is: Connecting to myjenkins:8080... connected. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. I used the next timeout values: 2, 8, 16, 32, 64, 128, 256, 1024 In all cases the error is the same. Does anybody knows a fix or workaround for this? ] |
Assignee | New: Manuel Recena Soto [ recena ] |
Workflow | Original: JNJira [ 148795 ] | New: JNJira + In-Review [ 186120 ] |