We have seeing the same problem. For some reason it is calling 'git rev-list' on a commit that is 6 months old. There doesn't seems to be anything particularly special about that commit (No release tag).
I did notice that if I skip the 'merge before build' it has a higher chance of working, but it makes the job much less useful. I don't think the git command is actually what is hanging, because when I run 'ps' I don't see any processes running on the slave or the master. It seems that the command finished, but the waiting process didn't get notified somehow? Any ideas how to debug this? I would like to see what is going on in the git plugin. Why is it picking that ancient commit? What does it want to do next? I tried adding a debug logger for 'hudson.plugins.git' and Log Level 'All' but I don't see anything useful. On Monday, February 5, 2018 at 1:48:25 AM UTC-7, Sverre Moe wrote: > > Just now we got one Multibranch pipeline to hang on git rev-list on a > project that has no git tags. > Running with latest Jenkins, git plugin, git-client plugin and git. > > mandag 5. februar 2018 09.17.03 UTC+1 skrev Sverre Moe følgende: >> >> The problem occurred with the latest version of git plugin and git client >> plugin. >> We have gotten the problem on projects that does not have many tags, >> aprox 300. We even got the problem on a project that has no tags at all. >> >> We are back at running with the latest version after I tried to revert >> back to the previous git-client-3.7.0 (was 3.7.1 and could not revert >> further back). On the server I have upgraded git to latest v2.16 (wanted to >> see if using a newer version of git would solve the problem). >> >> fredag 2. februar 2018 19.11.46 UTC+1 skrev Mark Waite følgende: >>> >>> The JENKINS-45447 and JENKINS-47169 fix in git client plugin 2.7.0 and >>> in git plugin 3.7.0 might be visible as a hang in `git rev-list`. Does >>> that repository contain a large number of tags? If so, then be sure you're >>> using the latest releases of git client plugin and git plugin. >>> >>> Mark Waite >>> >>> On Fri, Feb 2, 2018 at 4:14 PM Sverre Moe <[email protected]> wrote: >>> >>>> Recently we upgraded Jenkins from 2.100 to 2.103, and a bunch of >>>> plugins at the same time. >>>> After this we are frequently experiencing checkout scm to freeze at the >>>> last step in this process (git rev-list). It will hang there forever, way >>>> past the default 10 minutes timeout. >>>> >>>> Seems we are not the only one experiencing this problem, but while >>>> others have had this problem for quite some time we have only gotten it >>>> recently. >>>> https://issues.jenkins-ci.org/browse/JENKINS-46503 >>>> >>>> Anyone familiar with this problem? >>>> >>>> I was thinking of reverting back to Jenkins 2.100 and the following >>>> plugins >>>> git 3.6.4 >>>> git-client 2.6.0 >>>> I have downloaded the JAR files for these plugins. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/0a6cdca7-1a08-42e9-8e39-7fb2a10e287a%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/0a6cdca7-1a08-42e9-8e39-7fb2a10e287a%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b0b2a97b-326a-4a15-ad31-0be889a612d9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
