BigW Consortium Gitlab

  1. 03 Jun, 2016 1 commit
    • Replace colorize gem with rainbow. · 903946c7
      Connor Shea authored
      Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize.
      
      The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance.
      
      The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product.
      
      An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded.
      
      Rainbow library: https://github.com/sickill/rainbow
      Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
  2. 23 May, 2016 1 commit
  3. 16 May, 2016 1 commit
  4. 22 Mar, 2016 1 commit
  5. 19 Nov, 2015 1 commit
  6. 10 Nov, 2015 1 commit
    • Implement Build Artifacts · d0e3e823
      Kamil Trzcinski authored
      - Offloads uploading to GitLab Workhorse
      - Use /authorize request for fast uploading
      - Added backup recipes for artifacts
      - Support download acceleration using X-Sendfile
  7. 15 Sep, 2015 1 commit
  8. 23 Jun, 2015 1 commit
  9. 02 Apr, 2015 1 commit
  10. 20 Nov, 2014 2 commits
  11. 05 Aug, 2013 1 commit
  12. 03 Jun, 2013 1 commit
  13. 30 May, 2013 1 commit
    • fixes for gitlab restore with non-standard backup and repo dirs · 9c82bca5
      Angus MacArthur authored
      These fixes will allow a restore of gitlab when the backups and
      repositories directories are in non-standard locations (ie sub-dirs
      of gitlabhq).  Also allows the restore to be run from script
      overriding the need of a user to confirm the rebuild of the
      authorized_keys file.
  14. 08 May, 2013 1 commit
  15. 06 May, 2013 1 commit
  16. 05 May, 2013 1 commit
  17. 23 Apr, 2013 1 commit
  18. 18 Apr, 2013 1 commit
  19. 10 Apr, 2013 1 commit
  20. 05 Apr, 2013 2 commits
  21. 14 Mar, 2013 1 commit
  22. 11 Feb, 2013 1 commit
  23. 05 Jan, 2013 1 commit
  24. 31 Dec, 2012 2 commits
  25. 23 Dec, 2012 1 commit
  26. 22 Dec, 2012 1 commit
  27. 20 Dec, 2012 2 commits
  28. 22 Nov, 2012 1 commit
  29. 19 Nov, 2012 1 commit
  30. 26 Sep, 2012 1 commit
  31. 02 Sep, 2012 1 commit
  32. 28 Aug, 2012 2 commits
  33. 25 Aug, 2012 1 commit
  34. 27 Jul, 2012 1 commit
  35. 26 Jul, 2012 1 commit
    • Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and… · ec01cbef
      Michael van Rooijen authored
      Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).