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

Default MultiBranch Git LFS pull no longer works

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • git-plugin
    • Jenkins 2.487 JDK 21 on Ubuntu Linux 24.04.2

      I have multiple MultiBranch Pipelines making use of Jenkinsfiles.

      When upgrading from Jenkins version 2.486 to 2.487 and all newer versions, the default git checkout no longer does a git lfs pull, even though it shows it in the build console output.

      It also does not work by explicitly adding an extra Branch Source Behaviour of type "Git LFS pull after checkout"

       

      I have verified that git lfs is installed on the system.

      When I go to the workspace and check the lfs files, they are just the pointers to the repo.

      If I run git lfs pull manually in the workspace directory, it works and files get updated with remote LFS data.

      I have tried multiple versions of Jenkins, including the latest, with the same issue. 

      When I roll back to 2.486, it works again.

       

      I have done a diff between 2.486 and 2.487 https://github.com/jenkinsci/jenkins/compare/jenkins-2.486...jenkins-2.487

      The only change that I can see is related to the JSON lib.

       

      My versions of git tools are:

      git version 2.43.0

      git-lfs/3.4.1 (GitHub; linux amd64; go 1.22.2)

       

      Your help will be greatly appreciated.

        1. Jenkins 01.png
          Jenkins 01.png
          110 kB
        2. Jenkins 02.png
          Jenkins 02.png
          245 kB

          [JENKINS-75543] Default MultiBranch Git LFS pull no longer works

          Mark Waite added a comment -

          I've not seen any report from others about Git LFS not working at that transition. The change of JSON library is not expected to change the behavior of command line git in any way.

          Other things you might check:

          • Has the Bitbucket server configuration changed?
          • Have Bitbucket credentials changed?
          • What is the output if you enable git tracing?
          • What is the output if you enable additional diagnostics from git LFS?

          Mark Waite added a comment - I've not seen any report from others about Git LFS not working at that transition. The change of JSON library is not expected to change the behavior of command line git in any way. Other things you might check: Has the Bitbucket server configuration changed? Have Bitbucket credentials changed? What is the output if you enable git tracing? What is the output if you enable additional diagnostics from git LFS?

          Dirkco added a comment -

          Thank you for getting back to me.

          Your comments led me down a path of discovery.

          I forgot to mention that I am using Jenkins in Docker.

          What I have found is that from version 2.487 git lfs is no longer included in the base image.

          Previously, I verified that git lfs is installed on the host hosting Docker, not the Docker image where Jenkins is running.

          I updated my Dockerfile to install git lfs, and everything is working.

           

          Thank you

           

          Dirkco added a comment - Thank you for getting back to me. Your comments led me down a path of discovery. I forgot to mention that I am using Jenkins in Docker. What I have found is that from version 2.487 git lfs is no longer included in the base image. Previously, I verified that git lfs is installed on the host hosting Docker, not the Docker image where Jenkins is running. I updated my Dockerfile to install git lfs, and everything is working.   Thank you  

            Unassigned Unassigned
            rzrcdr Dirkco
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: