1. 16 Dec, 2016 3 commits
    • Rémy Coutable's avatar
      Merge branch '25301-git-2.11-force-push-bug' into 'master' · a3712cc1
      Rémy Coutable authored
      Pass relevant git environment variables while calling `/allowed`
      
      1. Starting version 2.11, git changed the way the pre-receive flow works.
        - Previously, the new potential objects would be added to the main repo. If the pre-receive passes, the new objects stay in the repo but are linked up. If the pre-receive fails, the new objects stay orphaned in the repo, and are cleaned up during the next `git gc`.
        - In 2.11, the new potential objects are added to a temporary "alternate object directory", that git creates for this purpose. If the pre-receive passes, the objects from the alternate object directory are migrated to the main repo. If the pre-receive fails the alternate object directory is simply deleted.
      2. In our workflow, the pre-recieve script calls the `/allowed` endpoint on the
         rails server. This `/allowed` endpoint calls out directly to git to perform
         various checks. These direct calls to git do _not_ have the necessary
         environment variables set which allow access to the "alternate object
         directory" (explained above). Therefore these calls to git are not able to
         access any of the new potential objects to be added during this push.
      
      3. We fix this by passing the relevant environment variables
         (`GIT_ALTERNATE_OBJECT_DIRECTORIES`, `GIT_OBJECT_DIRECTORY`, and
         `GIT_QUARANTINE_PATH`) to the `/allowed` endpoint, which will then include
         these environment variables while calling out to git.
      
      ---
      
      - Related to gitlab-org/gitlab-ce#25301. 
      - Corresponding backend MR: gitlab-org/gitlab-ce!7967
      - Corresponding EE MR: gitlab-org/gitlab-ee!964
      
      See merge request !112
      a3712cc1
    • Timothy Andrew's avatar
      Add CHANGELOG entry. · b72ee519
      Timothy Andrew authored
      b72ee519
    • Timothy Andrew's avatar
      Pass relevant git environment variables while calling `/allowed` · fc201648
      Timothy Andrew authored
      1. Starting version 2.11, git changed the way the pre-receive flow works.
      
        - Previously, the new potential objects would be added to the main repo. If the
          pre-receive passes, the new objects stay in the repo but are linked up. If
          the pre-receive fails, the new objects stay orphaned in the repo, and are
          cleaned up during the next `git gc`.
      
        - In 2.11, the new potential objects are added to a temporary "alternate object
          directory", that git creates for this purpose. If the pre-receive passes, the
          objects from the alternate object directory are migrated to the main repo. If
          the pre-receive fails the alternate object directory is simply deleted.
      
      2. In our workflow, the pre-recieve script calls the `/allowed` endpoint on the
         rails server. This `/allowed` endpoint calls out directly to git to perform
         various checks. These direct calls to git do _not_ have the necessary
         environment variables set which allow access to the "alternate object
         directory" (explained above). Therefore these calls to git are not able to
         access any of the new potential objects to be added during this push.
      
      3. We fix this by passing the relevant environment variables
         (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY, and
         GIT_QUARANTINE_PATH) to the `/allowed` endpoint, which will then include
         these environment variables while calling out to git.
      fc201648
  2. 12 Dec, 2016 3 commits
  3. 09 Dec, 2016 1 commit
  4. 08 Dec, 2016 1 commit
  5. 06 Dec, 2016 1 commit
  6. 01 Dec, 2016 23 commits
  7. 30 Nov, 2016 1 commit
  8. 17 Nov, 2016 2 commits
  9. 16 Nov, 2016 5 commits