Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-15652

Can't use git lfs in BuildConfig git source with strategy Docker

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • 4.10.z
    • Build
    • None
    • No
    • Pipeline Integrations #241
    • 1
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-15645. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-15643. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-15606. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-15497. The following is the description of the original issue:

      I am using a BuildConfig with git source and the Docker strategy. The git repo contains a large zip file via LFS and that zip file is not getting downloaded. Instead just the ascii metadata is getting downloaded. I've created a simple reproducer (https://github.com/selrahal/buildconfig-git-lfs) on my personal github. If you clone the repo

      git clone git@github.com:selrahal/buildconfig-git-lfs.git
      

      and apply the bc.yaml file with

      oc apply -f bc.yaml
      

      Then start the build with

      oc start-build test-git-lfs
      

      You will see the build fails at the unzip step in the docker file

      STEP 3/7: RUN unzip migrationtoolkit-mta-cli-5.3.0-offline.zip
      End-of-central-directory signature not found. Either this file is not
      a zipfile, or it constitutes one disk of a multi-part archive. In the
      latter case the central directory and zipfile comment will be found on
      the last disk(s) of this archive.
      

      I've attached the full build logs to this issue.

            cdaley Corey Daley
            openshift-crt-jira-prow OpenShift Prow Bot
            Corey Daley Corey Daley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: