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

Pipeline Git LFS avoid pull on Jenkins Master

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin
    • None

      When using declarative pipeline in a pipeline(not multibranch-pipeline) job and adding the additional behavior to "Git LFS pull after checkout".

      This is actually done on master too. Which for very LARGE files seems over kill.

      First off we don't have LFS installed on master.
      Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents...

      Unless I am mistaken I don't think this is the intended behavior.

      Of course I could try an extension plugin that says avoids LFS checkout on master.

      I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior.

          [JENKINS-53959] Pipeline Git LFS avoid pull on Jenkins Master

          Joseph Petersen (old) created issue -
          Joseph Petersen (old) made changes -
          Summary Original: Pipeline Git LFS avoid pull on master New: Pipeline Git LFS avoid pull on Jenkins Master
          Joseph Petersen (old) made changes -
          Priority Original: Blocker [ 1 ] New: Trivial [ 5 ]
          KY Lee made changes -
          Priority Original: Trivial [ 5 ] New: Minor [ 4 ]
          KY Lee made changes -
          Description Original: When using declarative pipeline and adding the additional behavior to "Git LFS pull after checkout"

          This is actually done on master too. Which for very LARGE files seems over kill.

          First off we don't have LFS installed on master.
          Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents... :)

          Unless I am mistaken I don't think this is the intended behavior.

          Of course I could try an extension plugin that says avoids LFS checkout on master.

          I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior.
          New: When using declarative pipeline in a pipeline(not multibranch-pipeline) job and adding the additional behavior to "Git LFS pull after checkout".

          This is actually done on master too. Which for very LARGE files seems over kill.

          First off we don't have LFS installed on master.
           Secondly we don't have that much storage allocated cause we never considered the master would be trying to pull from our LFS storage that is a job for our agents... :)

          Unless I am mistaken I don't think this is the intended behavior.

          Of course I could try an extension plugin that says avoids LFS checkout on master.

          I would be happy to look into a solution for the git plugin if this is indeed not the intended behavior.
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]

          Mark Waite added a comment -

          Extension plugin that allows optionally skipping LFS checkout on master seems like a reasonable approach in this case.

          A declarative Pipeline job (not multibranch) was assumed (by me anyway) that if it performs a checkout on the master (to get the Jenkinsfile, or for whatever other reason), it would use the same checkout as the agent uses. I'm not sure that my assumption was valid, only that it was my assumption.

          However, the GitHub Branch Source plugin, the Bitbucket Branch Source plugin, and the Gitea Branch Source plugin all use a REST API call to get the Jenkinsfile (for multibranch at least). If the purpose of the checkout on the master is just to obtain the Jenkinsfile, then I have no objection to an extension plugin that optionally skips LFS checkout on master.

          Mark Waite added a comment - Extension plugin that allows optionally skipping LFS checkout on master seems like a reasonable approach in this case. A declarative Pipeline job (not multibranch) was assumed (by me anyway) that if it performs a checkout on the master (to get the Jenkinsfile, or for whatever other reason), it would use the same checkout as the agent uses. I'm not sure that my assumption was valid, only that it was my assumption. However, the GitHub Branch Source plugin, the Bitbucket Branch Source plugin, and the Gitea Branch Source plugin all use a REST API call to get the Jenkinsfile (for multibranch at least). If the purpose of the checkout on the master is just to obtain the Jenkinsfile, then I have no objection to an extension plugin that optionally skips LFS checkout on master.
          Joseph Petersen made changes -
          Assignee New: Joseph Petersen [ jetersen ]
          Joseph Petersen made changes -
          Assignee Original: Joseph Petersen [ jetersen ] New: Mark Waite [ markewaite ]
          René Scheibe made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]

            Unassigned Unassigned
            casz Joseph Petersen (old)
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: