[JIRA] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves
Tomas Hellberg resolved JENKINS-17700 as Not A Defect Windows: Git clone fails on computer with multiple executors or slaves After more debugging, we observe the same problem while executing git directly outside the plugin, so it is not a Git plugin issue. Closing as Not A Defect. Change By: Tomas Hellberg (21/May/13 9:07 AM) Status: Open Resolved Resolution: NotADefect 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] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves
Tomas Hellberg created JENKINS-17700 Windows: Git clone fails on computer with multiple executors or slaves Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 22/Apr/13 1:10 PM Description: This problem relates to Git on Windows slaves. Git clone hangs indefinitely for about one in three builds on slaves with multiple executors, or on a computers with multiple slaves. If each slave is placed within a virtual machine on the same computer we experience no hangs. So the problem seems to be occurring when multiple "git clone" operations are executed at the same time on the same computer, regardless if the multiple executions of "git clone" are performed on on slave with multiple executors or on a computer with multiple slaves. Example build output: Triggered by Gerrit: http://gerrit.int/573 Building remotely on Slave 1h http://jenkins.int/computer/Slave%201h in workspace c:\Jenkins1h\workspace\Fw_BuildSystem_Verify Checkout:Fw_BuildSystem_Verify / c:\Jenkins1h\workspace\Fw_BuildSystem_Verify - hudson.remoting.Channel@1b53c3c6:Slave 1h Using strategy: Gerrit Trigger Last Built Revision: Revision 1387f2632ef7b7a576597a3eecfd0542e28d085f (develop) Cloning the remote Git repository Cloning repository ssh://gerrit.int:29418/Fw/Framework.git git --version git version 1.8.1.msysgit.1 Build was aborted Notifying upstream projects of job completion Finished: ABORTED Environment: Windows 7 x64, Jenkins 1.511, git version 1.8.1.msysgit.1 Project: Jenkins Priority: Major Reporter: Tomas Hellberg 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] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I downgraded to 1.2.0/1.03 and now I get com.thoughtworks.xstream.mapper.CannotResolveClassException: hudson.plugins.git.GitSCM Any ideas? 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] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ ... and Git is no longer a valid SCM option. 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] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Tomas Hellberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I managed now to get it working with 1.2.0/1.03. I believe that the problem was caused by a file git.hpi.disabled. I don't know why the plugin got disabled, but I'm up and running again now. Phew... 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] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Tomas Hellberg commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session For which release will this fix be available? I'm at 1.500 and still have to keep logging in over and over. 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] (JENKINS-15156) Builds Disappear from Build History after Completion
Tomas Hellberg commented on JENKINS-15156 Builds Disappear from Build History after Completion 12 hours later the history is back. This time without a master restart. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Tomas Hellberg updated JENKINS-15156 Builds Disappear from Build History after Completion Change By: Tomas Hellberg (01/Nov/12 8:13 AM) Environment: Jenkins1.477.2MasterandSlavesWindowsServer2008r2 (AlsoonJenkins1.488WindowsServer2008) 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Tomas Hellberg commented on JENKINS-15156 Builds Disappear from Build History after Completion I have the same problem on Jenkins ver. 1.488. Master is Windows server 2008. History showed correctly after upgrading to 1.488, but disappeared after next build, so now the history is empty. The build is visible during job execution but disappears after completion. 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
[JIRA] (JENKINS-13536) File parameter causing data lost after Jenkins restart
Tomas Hellberg commented on JENKINS-13536 File parameter causing data lost after Jenkins restart I need this also. 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
[JIRA] (JENKINS-13536) File parameter causing data lost after Jenkins restart
Tomas Hellberg commented on JENKINS-13536 File parameter causing data lost after Jenkins restart Still not working in 1.488. 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
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Tomas Hellberg commented on JENKINS-15156 Builds Disappear from Build History after Completion In my case, this might be related to JENKINS-13536, which causes loading of history to fail if the temp file store by the file upload plugin is removed. 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
