[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process If "dashboard-view" is the default Jenkins view (the "Standard Jenkins jobs list") then this is correct, assuming that's where the problem is (versus some other part of Jenkins that transacts with the dashboard-view plugin). 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic edited a comment on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process If "dashboard-view" is the default Jenkins view (appears so, looking at a snapshot of the "Standard Jenkins jobs list") then this is correct, assuming that's where the problem is (versus some other part of Jenkins that transacts with the dashboard-view plugin). 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I just updated to 1.510 (and updated the plugins) and this issue appears to be resolved. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic closed JENKINS-17186 as Fixed Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly This appears to be resolved. Change By: Martin Falatic (11/Apr/13 4:20 AM) Status: Resolved Closed 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic created JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Attachments: systeminfo.txt Components: dashboard-view Created: 11/Apr/13 4:40 AM Description: I just updated from Jenkins 1.504 today as part of resolving another outstanding issue. I notice that the main dashboard page is much slower to load than it was before, and also notice that the server gets high CPU load in the process (it gets super-bad if you try and reload it a few times, as one might do when a page seems frozen). This is not the case on the individual job pages, the "manage Jenkins" page or other such ancillary pages. My main page has quite a few jobs in the main view, but that didn't have an adverse effect before. It did have some trouble connecting to the slave, right after the update, but that appears to be working properly now. At the moment, several minutes after it seemed to have normalized a bit, I see one CPU is now completely spiked by Jenkins. Downgrading to 1.504 until this is resolved or explained. Environment: Jenkins 1.510 + gerrit 2.5.2 on Ubuntu 12.04. See attached systeminfo file for details as reported by Jenkins. Project: Jenkins Priority: Critical Reporter: Martin Falatic 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic updated JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Change By: Martin Falatic (11/Apr/13 4:55 AM) Description: IjustupdatedfromJenkins1.504todayaspartofresolvinganotheroutstandingissue.Inoticethatthemaindashboardpageismuchslowertoloadthanitwasbefore,andalsonoticethattheservergetshighCPUloadintheprocess(itgetssuper-badifyoutryandreloaditafewtimes,asonemightdowhenapageseemsfrozen).Thisisnotthecaseontheindividualjobpages,themanageJenkinspageorothersuchancillarypages.Mymainpagehasquiteafewjobsinthemainview,butthatdidnthaveanadverseeffectbefore.It*did*havesometroubleconnectingtotheslave,rightaftertheupdate,butthatappearstobeworkingproperlynow.Atthemoment,severalminutesafteritseemedtohavenormalizedabit,IseeoneCPUisnowcompletelyspikedbyJenkins. Downgrading Downgraded to1. 504 505+git-client1.03 untilthisisresolvedorexplained. Note:afterthedowngradethingsarebacktobeingspeedy.Dashboardloadsqicklyonopeningitoronswitchingtoit,andanyCPUloadisverybrief(versuswaitingseveralsecondsforthepagetodisplay,ormuchlongerifitwasrefreshedafewtimes).Ihitreloadseveraltimesinsuccession...itwasreloadedinasecondwithnomajorloadontheCPU(versuswaitingaround30secondsforthepagetofinallyappearonthenewerversion).Note2:evenin1.505youendupwithoneJenkins-bearingCPUthatstubbornlyspikesat100%afterafewquickreloads...andappearstostaythatway.Sothatpersistentspikemaynotbepartofthesameissuebutiscertainlyinteresting. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic updated JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Change By: Martin Falatic (11/Apr/13 4:56 AM) Description: IjustupdatedfromJenkins1.504todayaspartofresolvinganotheroutstandingissue.Inoticethatthemaindashboardpageismuchslowertoloadthanitwasbefore,andalsonoticethattheservergetshighCPUloadintheprocess(itgetssuper-badifyoutryandreloaditafewtimes,asonemightdowhenapageseemsfrozen).Thisisnotthecaseontheindividualjobpages,themanageJenkinspageorothersuchancillarypages.Mymainpagehasquiteafewjobsinthemainview,butthatdidnthaveanadverseeffectbefore.It*did*havesometroubleconnectingtotheslave,rightaftertheupdate,butthatappearstobeworkingproperlynow.Atthemoment,severalminutesafteritseemedtohavenormalizedabit,IseeoneCPUisnowcompletelyspikedbyJenkins.Downgradedto1.505+git-client1.03untilthisisresolvedorexplained.Note 1 : after After thedowngradethingsarebacktobeingspeedy. Dashboard Thedashboard loads qickly quickly onopeningitoronswitchingtoit,andanyCPUloadisverybrief(versuswaitingseveralsecondsforthepagetodisplay,ormuchlongerifitwasrefreshedafewtimes).Ihitreloadseveraltimesinsuccession...itwasreloadedinasecondwithnomajorloadontheCPU(versuswaitingaround30secondsforthepagetofinallyappearonthenewerversion). Note2 Note2 : even Even in1.505youendupwithoneJenkins-bearingCPUthatstubbornlyspikesat100%afterafewquickreloads...andappearstostaythatway (ifyoureloadafewmoretimesyoustillendupwiththiscondition,thoughitmightbeonanotherCPUinthesystem) .So that the persistent CPU spikemay ormay notbe partofthesame relatedtothis issue butiscertainlyinteresting . 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic updated JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Change By: Martin Falatic (11/Apr/13 4:57 AM) Description: IjustupdatedfromJenkins1. 504 505 todayaspartofresolvinganotheroutstandingissue.Inoticethatthemaindashboardpageismuchslowertoloadthanitwasbefore,andalsonoticethattheservergetshighCPUloadintheprocess(itgetssuper-badifyoutryandreloaditafewtimes,asonemightdowhenapageseemsfrozen).Thisisnotthecaseontheindividualjobpages,themanageJenkinspageorothersuchancillarypages.Mymainpagehasquiteafewjobsinthemainview,butthatdidnthaveanadverseeffectbefore.It*did*havesometroubleconnectingtotheslave,rightaftertheupdate,butthatappearstobeworkingproperlynow.Atthemoment,severalminutesafteritseemedtohavenormalizedabit,IseeoneCPUisnowcompletelyspikedbyJenkins.Downgradedto1.505+git-client1.03untilthisisresolvedorexplained.Note1:Afterthedowngradethingsarebacktobeingspeedy.Thedashboardloadsquicklyonopeningitoronswitchingtoit,andanyCPUloadisverybrief(versuswaitingseveralsecondsforthepagetodisplay,ormuchlongerifitwasrefreshedafewtimes).Ihitreloadseveraltimesinsuccession...itwasreloadedinasecondwithnomajorloadontheCPU(versuswaitingaround30secondsforthepagetofinallyappearonthenewerversion).Note2:Evenin1.505youendupwithoneJenkins-bearingCPUthatstubbornlyspikesat100%afterafewquickreloads...andappearstostaythatway(ifyoureloadafewmoretimesyoustillendupwiththiscondition,thoughitmightbeonanotherCPUinthesystem).SothepersistentCPUspikemayormaynotberelatedtothisissue. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process On that persistent CPU thing: several full refreshes of the Jenkins dashboard page (crtl-shift-F5 in Windows) is quite effective at spiking not just one but several CPUs at once. I'm curious if this is a known issue or how to track down where the problem is. As relates to this present 1.510 issue, even with almost all the cores maxed out because of this weird persistent CPU thing, 1.505 still loads and presents the dashboard quickly. 1.510 would just get worse and worse the more you hammered it. Now, on the prudence of actually refreshing this much: At this point I'm testing the boundaries of this issue. Obviously this isn't a great thing to do, but the tool shouldn't have persistent adverse side-effects because of it, and performance completely tanks in 1.510 if you do this even a little (it was the lag on switching back to the dashboard view that caused me to refresh and trigger this in the first place, and to notice how much extra time even a couple of loads/refreshes added to an already extended load time). A few users accessing the dashboard at once would have a similar effect in terms of simultaneous load, with no doubt similar unpleasant results. 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] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Martin Falatic edited a comment on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process On that persistent CPU thing: several full refreshes of the Jenkins dashboard page (shift-ctrl-R in Windows) is quite effective at spiking not just one but several CPUs at once. I'm curious if this is a known issue or how to track down where the problem is. As relates to this present 1.510 issue, even with almost all the cores maxed out because of this weird persistent CPU thing, 1.505 still loads and presents the dashboard quickly. 1.510 would just get worse and worse the more you hammered it. Now, on the prudence of actually refreshing this much: At this point I'm testing the boundaries of this issue. Obviously this isn't a great thing to do, but the tool shouldn't have persistent adverse side-effects because of it, and performance completely tanks in 1.510 if you do this even a little (it was the lag on switching back to the dashboard view that caused me to refresh and trigger this in the first place, and to notice how much extra time even a couple of loads/refreshes added to an already extended load time). A few users accessing the dashboard at once would have a similar effect in terms of simultaneous load, with no doubt similar unpleasant results. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Indeed. I realize there's a drive to move to Jgit for git-client, but it's apparently not ready for prime time when it comes to complex filesystems in Unix. More info on git's "procelain" versus "plumbing" (and the counter-intuitive use of the term porcelain versus the option "--porcelain") can be found here: http://stackoverflow.com/a/6978402/760905 Since other VCS plugins were switched to pure Java versions, do those plugins handle symlinks and other low-level, OS-dependent features properly? (Of course CVS doesn't know about symlinks to begin with, but SVN certainly does.) 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I updated to plugins git 1.3.0 and git-client 1.0.4, then updated the git-client to this snapshot, then restarted Jenkins and re-triggered an affected build. The test failed, though differently than before (output below). Note: after this, I did have the option to downgrade git-client to 1.0.3, just like 1.2.0 for git. I clicked both, then restarted, but again the git-client never actually downgraded (and I lost the option to downgrade that one after the reboot). Strange. I manually downgraded it to restore normal functionality. Commencing build of Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) Checking out Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) FATAL: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc hudson.plugins.git.GitException: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:246) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) ... 16 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:1011) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:242) ... 17 more 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic edited a comment on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I updated to plugins git 1.3.0 and git-client 1.0.4, then updated the git-client to the 1.0.5 test snapshot, then restarted Jenkins and re-triggered an affected build. The test failed, though differently than before (output below). Note: after this, I did have the option to downgrade git-client to 1.0.3, just like 1.2.0 for git. I clicked both, then restarted, but again the git-client never actually downgraded (and I lost the option to downgrade that one after the reboot). Strange. I manually downgraded it to restore normal functionality. Commencing build of Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) Checking out Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) FATAL: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc hudson.plugins.git.GitException: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:246) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) ... 16 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:1011) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:242) ... 17 more 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I can't explain why that symlink is necessary though I believe it was/is related to the operation of the puppet module involved (I'm not the direct developer of the code itself). It probably resolves differently on the target system (the symlink is ../../.. and the path apt/spec/fixtures may itself have symlinks involved). That aside, it's unexpected behavior when a change like this breaks Jenkins even though git itself remains perfectly happy with such symlinks (it took a while to figure out where the problem was occurring so I could get our systems back online). It does appear to be a bug in Jgit, and this transition to Jgit opens Jenkins up to other Jgit bugs as well. What drove this sudden switch away from normal git (which is more robust and feature-rich overall)? And for all this, it would be useful to have the git-client in the list of plugins: it would have saved a lot of time during the downgrade process. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic updated JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I'm changing this to a blocker because the only workaround is to downgrade the git plugins (or to entirely sidestep Jgit as suggested in other recent bugs). Change By: Martin Falatic (14/Mar/13 6:10 AM) Priority: Major Blocker 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Note that I was able to downgrade the git plugin directly in the UI, but I had to actually do the git-client one manually. They're all available at: http://updates.jenkins-ci.org/download/plugins/ 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly When you say "the same" you mean you also have recursive symlinks? Also, did the plugin downgrade successfully resolve the issue for you? 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Marty Falatic created JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: systemInfo.txt Components: git Created: 13/Mar/13 6:12 AM Description: If a recursive symlink is present in one's git repo the new git/git-client plugins will fail badly as shown below. While having such a symlink may not be ideal, until git 1.3.0/ git-client 1.0.4 Jenkins did not have problems with it (nor have I had any other git client or tool fail because of this symlink). This appears to be specifically related to changes in the new git 1.3.0 plugin or its dependency git-client 1.0.4. Downgrading to the git 1.2.0 plugin and manually downgrading to the git-client 1.0.3 plugin was enough to remove this issue entirely. The problems seems specific to jgit. Note that I'm using Jenkins 1.505 and all other plugins are up-to-date. The details below contrast the working and broken builds (the only difference is the versions of the git plugins and their effects). A normal build (when using git 1.2.0 and git-client 1.0.3): Retriggered by user myself for Gerrit: http://gerritserver/710 Building on master in workspace /var/lib/jenkins/jobs/puppet/workspace Checkout:workspace / /var/lib/jenkins/jobs/puppet/workspace - hudson.remoting.LocalChannel@1307e9af Using strategy: Gerrit Trigger Last Built Revision: Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Using shallow clone Wiping out workspace first. Cloning the remote Git repository Cloning repository git://gitserver/puppet git --version git version 1.7.9.5 Fetching upstream changes from origin Commencing build of Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Checking out Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) workspace $ /bin/bash -ex /tmp/hudson3918244826320546803.sh --== ...and so on to a successful build ==-- Build break (when using git 1.3.0 and git-client 1.0.4): Retriggered by user myself for Gerrit: http://gerritserver/710 Building on master in workspace /var/lib/jenkins/jobs/puppet/workspace Checkout:workspace / /var/lib/jenkins/jobs/puppet/workspace - hudson.remoting.LocalChannel@6f0bc962 Using strategy: Gerrit Trigger Last Built Revision: Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Using shallow clone Wiping out workspace first. Cloning the remote Git repository Cloning repository git://gitserver/puppet git --version git version 1.7.9.5 Commencing build of Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) Checking out Revision b3f2bd79784969bd18866ff666f0ab46136ff196 (mybranch) FATAL: Could not checkout b3f2bd79784969bd18866ff666f0ab46136ff196 hudson.plugins.git.GitException: Could not checkout b3f2bd79784969bd18866ff666f0ab46136ff196 at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at
