Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42712

Github organization folder projects implicitly pull down git lfs, and fails to do so

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • github-organization-folder-plugin
    • None
    • Jenkins 2.32
      github-organization-folder 1.6
      git 3.1.0
      git-client 2.3.0

      A checkout scm step on a pull request of a private repository fails with:

      GitHub has been notified of this commit’s build result

hudson.plugins.git.GitException: Could not checkout 2c40576bf1c0677c56ee4f593e76599666620809
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2101)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1139)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83)
	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
	at hudson.security.ACL.impersonate(ACL.java:221)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2c40576bf1c0677c56ee4f593e76599666620809" returned status code 128:
stdout: 
stderr: Downloading sample.heavy (2.00 MB)
Error downloading object: sample.heavy (f4e68d3c34ad81c894a6aeedec14c7a4b867fbd5683ce3818bea5f29e019d744)

Errors logged to /ext/jenkins/workspace/rum_PR-22-DFTRGNR7GK7OAKHLPGP4/.git/lfs/objects/logs/20170313T102733.433291396.log
Use `git lfs logs last` to view the log.
error: external filter git-lfs smudge -- %f failed 2
error: external filter git-lfs smudge -- %f failed
fatal: sample.heavy: smudge filter lfs failed

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1793)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$800(CliGitAPIImpl.java:64)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:2078)
	... 12 more
Finished: FAILURE

      The same pipeline passes this step when built directly, rather than with the Organization Folder plugin.

          [JENKINS-42712] Github organization folder projects implicitly pull down git lfs, and fails to do so

          Giorgio Sironi added a comment -

          If I make the repository public, the build continues; so this is likely an issue with authentication not being provided correctly.
          However, what I am looking for is a way to disable the git lfs additional behavior; it's not necessary to explicitly pull down LFS resources for all builds as this is done in a new workspace, and each build would pull down hundreds of megabytes, rapidly hitting Github bandwidth limits on LFS.

          Giorgio Sironi added a comment - If I make the repository public, the build continues; so this is likely an issue with authentication not being provided correctly. However, what I am looking for is a way to disable the git lfs additional behavior; it's not necessary to explicitly pull down LFS resources for all builds as this is done in a new workspace, and each build would pull down hundreds of megabytes, rapidly hitting Github bandwidth limits on LFS.

          Stephen Connolly added a comment -

          Likely this will be fixed as part of JENKINS-43426

          Stephen Connolly added a comment - Likely this will be fixed as part of  JENKINS-43426

          Stephen Connolly added a comment -

          Should be fixed now as a side-effect of JENKINS-43507

          Stephen Connolly added a comment - Should be fixed now as a side-effect of JENKINS-43507

            kohsuke Kohsuke Kawaguchi
            giorgiosironi Giorgio Sironi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: