1. 06 Feb, 2018 5 commits
  2. 22 Jan, 2018 1 commit
  3. 29 Nov, 2017 1 commit
  4. 22 Nov, 2017 1 commit
  5. 17 Nov, 2017 1 commit
  6. 14 Nov, 2017 1 commit
  7. 18 Sep, 2017 2 commits
  8. 06 Sep, 2017 1 commit
  9. 31 Aug, 2017 1 commit
  10. 07 Jul, 2017 1 commit
  11. 16 Jun, 2017 1 commit
  12. 05 Jun, 2017 1 commit
  13. 03 May, 2017 1 commit
    • Alejandro Rodríguez's avatar
      Generate and handle a gl_repository param to pass around components · c45341c8
      Alejandro Rodríguez authored
      This new param allows us to share project information between components
      that don't share or don't have access to the same filesystem
      mountpoints, for example between Gitaly and Rails or between Rails and
      Gitlab-Shell hooks. The previous parameters are still supported, but if
      found, gl_repository is prefered. The old parameters should be deprecated
      once all components support the new format.
      c45341c8
  14. 14 Apr, 2017 2 commits
  15. 10 Apr, 2017 1 commit
  16. 03 Mar, 2017 1 commit
  17. 03 Feb, 2017 1 commit
  18. 16 Dec, 2016 1 commit
    • Timothy Andrew's avatar
      Accept environment variables from the `pre-receive` script. · f82d549d
      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 (in `gitlab-shell) calls the
         `/allowed` endpoint, which 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 accepting the relevant environment variables
         (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the
         `/allowed` endpoint, and then include these environment variables while
         calling out to git.
      
      4. This commit includes (whitelisted) these environment variables while making
         the "force push" check. A `Gitlab::Git::RevList` module is extracted to
         prevent `ForcePush` from being littered with these checks.
      f82d549d
  19. 16 Nov, 2016 1 commit