[JIRA] (JENKINS-13945) Copy artifacts from master - slaves takes about 10x longer with openjdk

2012-06-06 Thread lean...@1stplayable.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163563#comment-163563
 ] 

Leander Hasty commented on JENKINS-13945:
-

We're seeing something like this as well, on an upgrade from 1.455 to 1.466.  
It's much worse in our case: a build that is normally 20 minutes takes ~2 
hours and may or may not complete successfully; usually it stalls on archiving 
artifacts, but we also see ludicrous delays downloading anything but the 
smallest files directly from the workspace.  The console view also appears to 
be very behind reality.

These slaves are all Ubuntu 10.04 LTS (they're actually running in VMWare on 
Windows XP 32-bit and 64-bit hosts).  If we upgrade from the openjdk-6-jre 
package (6b20-1.9.13-0ubuntu version):


$ java -version
java version 1.6.0_20
OpenJDK Runtime Environment (IcedTea6 1.9.13) (6b20-1.9.13-0ubuntu1~10.04.1)
OpenJDK Client VM (build 19.0-b09, mixed mode, sharing)



... to a Java 7 package from Sun (via the Repository instructions at 
http://www.duinsoft.nl/packages.php?t=en ), the problem appears to go away.  
I've not yet tried other variants.

 Copy artifacts from master - slaves takes about 10x longer with openjdk
 

 Key: JENKINS-13945
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13945
 Project: Jenkins
  Issue Type: Bug
  Components: core
 Environment: Debian 6
Reporter: sanga

 Version: 1.451
 We switched from sun java to openjdk and noticed that copying artifacts from 
 master to slave took way longer than it had previously (x10 or more). 
 Switching back to sun java fixed the problem.
 Related to this, the node ping times, as seen at: 
 https://.../jenkins/computer/ were all up around 0.5s with openjdk and then 
 when switching to sun java dropped back down to where they should be (around 
 20ms).
 If this is a bug in openjdk that's not really Jenkins problem, but perhaps 
 there's something in Jenkins to be done. Or at least it'd be beneficial for 
 Jenkins to know about this I guess.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals

2012-05-16 Thread lean...@1stplayable.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162834#comment-162834
 ] 

Leander Hasty commented on JENKINS-6450:


Odd, I thought I had.  Vote placed.  At the moment we had to revert to polling 
every so hour or so to supplement the push notifications, and that's still less 
than ideal.  Since a patch might make this all go faster, I'll see what I can 
put together, but no promises -- the studio is quite busy at the moment.

 post-commit hook does no handle svn:externals
 -

 Key: JENKINS-6450
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll 
 SCM enabled and left empty 
Reporter: Axel Heider

 I've set up a post-commit hook that send a post request with the changed 
 files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It 
 works fine except for changes in directories or files referenced via 
 svn:externals. If something changes there, the project is no rebuild. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals

2012-03-26 Thread lean...@1stplayable.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160787#comment-160787
 ] 

Leander Hasty commented on JENKINS-6450:


I have the same issue with Jenkins v1.455 and v1.456 (currently rolled back to 
v1.455 due to unrelated bug JENKINS-13202), running under Tomcat on Mac OS X 
Server, with Subversion plugin 1.37 -- about to try an upgrade to Subversion 
plugin 1.39, but I see nothing in the changelog that makes me hopeful.

 post-commit hook does no handle svn:externals
 -

 Key: JENKINS-6450
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll 
 SCM enabled and left empty 
Reporter: Axel Heider

 I've set up a post-commit hook that send a post request with the changed 
 files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It 
 works fine except for changes in directories or files referenced via 
 svn:externals. If something changes there, the project is no rebuild. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals

2012-03-26 Thread lean...@1stplayable.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leander Hasty reopened JENKINS-6450:



 post-commit hook does no handle svn:externals
 -

 Key: JENKINS-6450
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll 
 SCM enabled and left empty 
Reporter: Axel Heider

 I've set up a post-commit hook that send a post request with the changed 
 files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It 
 works fine except for changes in directories or files referenced via 
 svn:externals. If something changes there, the project is no rebuild. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-6450) post-commit hook does no handle svn:externals

2012-03-26 Thread lean...@1stplayable.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160788#comment-160788
 ] 

Leander Hasty commented on JENKINS-6450:


Confirmed in Subversion plugin 1.39 as well.  We have one project that is based 
in this repository, and it was built:

Mar 26, 2012 1:16:30 PM hudson.triggers.SCMTrigger$Runner run
INFO: SCM changes detected in lib-docs. Triggering  #263

...but almost every other project we have has this as an extern and was not 
triggered.  Reopening the bug, hopefully this is the right action to take -- 
please let me know if you'd prefer I create a new bug.

 post-commit hook does no handle svn:externals
 -

 Key: JENKINS-6450
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, Poll 
 SCM enabled and left empty 
Reporter: Axel Heider

 I've set up a post-commit hook that send a post request with the changed 
 files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It 
 works fine except for changes in directories or files referenced via 
 svn:externals. If something changes there, the project is no rebuild. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira