[JIRA] [subversion-plugin] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Title: Message Title Richard Bergoin assigned an issue to Richard Bergoin Jenkins / JENKINS-24802 notifyCommit don't trigger a build if two svn repositories have same url start Change By: Richard Bergoin Assignee: Richard Bergoin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Title: Message Title Richard Bergoin commented on JENKINS-24802 Re: notifyCommit don't trigger a build if two svn repositories have same url start The PR to solve this is still opened : https://github.com/jenkinsci/subversion-plugin/pull/99 I want to recommend you to use the build artifacts (like in this integration : https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/491/org.jenkins-ci.plugins$subversion/), but the 99 PR integration has been deleted : https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/467/ leads to a 404. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-26778) Build-timeout+Plugin global timeout setting
Richard Bergoin created JENKINS-26778 Build-timeout+Plugin global timeout setting Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: build-timeout-plugin Created: 04/Feb/15 1:00 PM Description: With many jobs, it is a pain to set timeout on each job. Having a global setting (than can be overrided in job configuration) can be more simple. Project: Jenkins Priority: Minor Reporter: Richard Bergoin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin commented on JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start @Andreas Isn't your issue related to : https://issues.jenkins-ci.org/browse/JENKINS-22078 This one is to correct the repo list management (in []) : Could not find http://hostname/svn/BLACKOPS/ant-scripts in http://hostname/svn/BLACK, http://hostname/svn/NAMEofAthirdREPO The http://hostname/svn/BLACKOPS repo won't appear in the list because of an error (String startsWith misuse), so that it will use http://hostname/svn/BLACK instead. Do you use the plugin compiled from cloudbees ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin commented on JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start Ok, fixed it this time with PR 99 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Richard Bergoin edited a comment on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Maybe you can install and provide feedback using this snapshot : https://jenkins.ci.cloudbees.com/job/plugins/job/ci-game-plugin/23/org.jenkins-ci.plugins$ci-game/ EDIT : I just installed it : ci-game scored: 1.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin stopped work on JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start Change By: Richard Bergoin (23/Sep/14 8:14 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin started work on JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start Change By: Richard Bergoin (23/Sep/14 8:14 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin resolved JENKINS-24802 as Fixed notifyCommit dont trigger a build if two svn repositories have same url start Solved with pull request : https://github.com/jenkinsci/subversion-plugin/pull/98 Change By: Richard Bergoin (23/Sep/14 8:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin commented on JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start It seems I've introduced a regression (https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/org.jenkins-ci.plugins$subversion/414/testReport/junit/hudson.scm/SubversionSCMTest/testIgnoreExternals/) but all tests are OK on my dev host. I'm runing test using : mvn install This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin reopened JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start cf regression https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/org.jenkins-ci.plugins$subversion/414/testReport/junit/hudson.scm/SubversionSCMTest/testIgnoreExternals/ Change By: Richard Bergoin (23/Sep/14 8:59 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin created JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start Issue Type: Bug Assignee: Richard Bergoin Components: subversion Created: 22/Sep/14 1:03 PM Description: In SubversionRepositoryStatus 's onNotify method, UUID cache checks that UUID is in cache using the String 's startsWith method for a repo. But when having of two jobs with these svn repos/modules configured : https://svn.company.com/repo-client https://svn.company.com/repo-client-project-one The UUID check for https://svn.company.com/repo-client-project-one will use the UUID of https://svn.company.com/repo-client because https://svn.company.com/repo-client-project-one starts with https://svn.company.com/repo-client. This bug was introduced by myself when optimzing (e.g. caching) repositories URLs - UUIDs. @see https://github.com/jenkinsci/subversion-plugin/blob/subversion-2.3/src/main/java/hudson/scm/SubversionRepositoryStatus.java Project: Jenkins Priority: Major Reporter: Richard Bergoin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin updated JENKINS-24802 notifyCommit dont trigger a build if two svn repositories have same url start By patchgin the LOGGER : "Using cached uuid " + remoteUUID + " for module location " + urlFromConfiguration + " of job "+ p); Using cached uuid 70c81930-3579-417b-92ab-7213703bae7f for module location https://svn.company.com/repo-client-project-one/trunk of job hudson.model.FreeStyleProject@1aaf678cclient-project-one But when checking UUID, I'll get a different one : $ svn info https://svn.company.com/repo-client-project-one/trunk Path: trunk URL: https://svn.company.com/repo-client-project-one/trunk Repository Root: https://svn.company.com/repo-client-project-one Repository UUID: 96c3df3d-2883-4879-ab24-a4a5f8aeae3f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Daniel Just installed https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/336/org.jenkins-ci.plugins$subversion/ and removed ~/.subversion that contains "static credentials" added by using jsvn. And got the issue again on externals : Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed Re-added credentials by doing a "jsvn info $REPO", and then post-commit works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Daniel, thanks for reply, here is the log, and the CredentialsSVNAuthenticationProviderImpl logger output make me think that the credentials used for the externals are the one used for the main module (no additional module configured, as you said) : Apr 01, 2014 9:24:45 AM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl Attempting auth for URL: https://svn.company.com/repo/tags/project-1.0; Realm: https://svn.company.com:443 SVN repository Apr 01, 2014 9:24:45 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify Failed to handle Subversion commit notification org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /repo/tags/project-1.0 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2712) at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:202) at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials To clarify, you have one module configured, and no additional credentials? : yes. The realm for the external is (I think) the same that the realm of the "main" module, for exemple, an app have an external to a library tag : https://svn.company.com/app/trunk have https://svn.company.com/lib/tags/project-1.0 as externals Shouldn't main module credentials be applied, as both realms are "https://svn.company.com:443 SVN repository" ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I was thinking the PR 70 will solve this issue (I misundertood the log and think that it inform the "realm" which will be used to the connection). I can test this issue (as previously with PR 74), if the "possibly" can be assume to be "yes" (but who can decide of this...). From my point of view, credentials are "server based" for continuous, but it could be "repository based" (subpath of a server). Maybe a "FINE" logging of username used to connect to a repository can be interesting (for debugging purpose). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Jens, Ok for repo base credentials, in fact this is also that we have, I would add a "global credentials" to not have to reconfigure each jobs using this external (more than 30), but the global credentials is domain based (e.g. hostname, so only one global credential for svn.company.com) Note that we also have CI for our internal libraries, so the credentials are already entered in another job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Facing the same issue, and installed the latest github version with #70 pull request merged (https://github.com/jenkinsci/subversion-plugin/commit/ed6e43e04ddd15ce302b23740625ca4e69d1fead) which allows to log credentials used. The credentials are OK, so this bug might be linked to a svnkit one : http://issues.tmatesoft.com/issue/SVNKIT-345 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Update : installing current svnkit (https://github.com/jenkinsci/svnkit/releases/tag/1.7.10) cli tools, and making a "jsvn info $REPO" and saving credentials from there make post-commits working again. Not a good way, but it could help solving this issue temporaly waiting the 2.3 plugin version that correct it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Richard Bergoin commented on JENKINS-17616 Performance issue with Subversion plugin - trigger build on SVN commit takes too long We were having a similar issue after 1.43 - 1.54 plugin upgrade : our post-commit hook was during from 2 minutes to 5 minutes... and sometimes the job ended before the commit... We have 75 jobs with 1 svn location, and each uses two or more externals that are common of multiple repositories (some jobs are also using same location to a trunk). I've patched the doNotifyCommit method and our post commit now is around 20 seconds The issue is in the UUID determination method that makes an svn call (https in our case) and repeat this call for each locations. I have just add a simple "cache" map that prevents newer calls on already gathered UUIDs. Here is the pull request : https://github.com/jenkinsci/subversion-plugin/pull/59 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Richard Bergoin edited a comment on JENKINS-17616 Performance issue with Subversion plugin - trigger build on SVN commit takes too long We were having a similar issue after 1.43 - 1.54 plugin upgrade : our post-commit hook was during from 2 minutes to 5 minutes... and sometimes the job ended before the commit... We have 75 jobs with 1 svn location, and each uses two or more externals that are common of multiple repositories (some jobs are also using same location to a trunk). I've patched the doNotifyCommit method and our post commit now is around 20 seconds The issue is in the UUID determination method that makes an svn call (https in our case) and repeat this call for each locations. I have just add a simple "cache" map that prevents newer calls on already gathered UUIDs. Here is the pull request : https://github.com/jenkinsci/subversion-plugin/pull/59 EDIT to be more precise on results (20 seconds were measured at client side, including upload commit time, at server side, it lower : 11 seconds) : with UUID caching : Dec 12, 2013 9:41:35 PM FINE hudson.scm.SubversionRepositoryStatus Starting subversion locations checks for all jobs Dec 12, 2013 9:41:37 PM FINE hudson.scm.SubversionRepositoryStatus Scheduling the immediate polling of hudson.model.FreeStyleProject@25a598f5test-job Dec 12, 2013 9:41:37 PM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@25a598f5test-job Dec 12, 2013 9:41:37 PM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run Dec 12, 2013 9:41:42 PM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in test-job. Triggering #137 Dec 12, 2013 9:41:46 PM FINE hudson.scm.SubversionRepositoryStatus Ended subversion locations checks for all job without UUID caching : Dec 12, 2013 10:15:13 PM FINE hudson.scm.SubversionRepositoryStatus Starting subversion locations checks for all jobs Dec 12, 2013 10:15:40 PM FINE hudson.scm.SubversionRepositoryStatus Scheduling the immediate polling of hudson.model.FreeStyleProject@350d5a52test-job Dec 12, 2013 10:15:40 PM FINE hudson.triggers.SCMTrigger Scheduling a polling for hudson.model.FreeStyleProject@350d5a52test-job Dec 12, 2013 10:15:40 PM FINE hudson.triggers.SCMTrigger scheduling the trigger to (asynchronously) run Dec 12, 2013 10:15:51 PM INFO hudson.triggers.SCMTrigger$Runner run SCM changes detected in test-job. Triggering #138 Dec 12, 2013 10:18:20 PM FINE hudson.scm.SubversionRepositoryStatus Ended subversion locations checks for all jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mysql-auth] (JENKINS-17631) Mysql port number not used
Richard Bergoin created JENKINS-17631 Mysql port number not used Issue Type: Bug Affects Versions: current Assignee: Richard Bergoin Components: mysql-auth Created: 16/Apr/13 12:29 PM Due Date: 16/Apr/13 12:00 AM Project: Jenkins Priority: Major Reporter: Richard Bergoin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mysql-auth] (JENKINS-17631) Mysql port number not used
Richard Bergoin commented on JENKINS-17631 Mysql port number not used Sent a pull request fixing this issue : https://github.com/jenkinsci/mysql-auth-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mysql-auth] (JENKINS-17631) Mysql port number not used
Richard Bergoin started work on JENKINS-17631 Mysql port number not used Change By: Richard Bergoin (16/Apr/13 1:11 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mysql-auth] (JENKINS-17634) Password SHA-1 encoding returns SHA-1 Message Digest from SUN, in progress
Richard Bergoin started work on JENKINS-17634 Password SHA-1 encoding returns SHA-1 Message Digest from SUN, in progress Change By: Richard Bergoin (16/Apr/13 1:26 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
