BigW Consortium Gitlab

  1. 29 Sep, 2017 1 commit
  2. 01 Aug, 2017 1 commit
  3. 04 May, 2017 1 commit
  4. 13 Apr, 2017 1 commit
    • Expand components version specification format to allow branches · e61325ff
      Alejandro Rodríguez authored
      Currently we specify versions for Gitlab-Shell, Workhorse and Gitaly
      using version strings, to which we prepend 'v' and assume are tags.
      These changes allow branches or tags with other name formats to be
      specified by prepending '=' to the version string (á la govendor).
      
      We also simplify the process to reset to the given version (now a
      branch or tag): Right now there's a check to supposedly try to avoid
      fetching from the remote the version if it already exist locally. But
      the previous logic already clones if the directory doesn't exist or
      fetches if it does, so this check is pointless. We can safely assume the
      version exists once we get to the reset stage.
  5. 23 Feb, 2017 1 commit
  6. 30 Nov, 2016 1 commit
  7. 01 Nov, 2016 1 commit
  8. 06 Oct, 2016 1 commit
  9. 11 Aug, 2016 1 commit
  10. 03 Aug, 2016 1 commit
  11. 30 Jun, 2016 2 commits
  12. 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
  13. 03 Nov, 2015 1 commit
  14. 23 Jun, 2015 1 commit
  15. 03 Jun, 2015 1 commit
  16. 20 Mar, 2015 1 commit
  17. 12 Dec, 2014 2 commits
  18. 11 Dec, 2014 1 commit
  19. 18 Nov, 2014 2 commits
  20. 05 Nov, 2014 2 commits
  21. 18 Oct, 2014 2 commits
  22. 15 Oct, 2014 1 commit
  23. 22 Sep, 2014 2 commits
  24. 26 Aug, 2014 1 commit
  25. 31 Jul, 2014 2 commits
  26. 02 May, 2014 2 commits
  27. 08 Apr, 2014 1 commit
  28. 14 Mar, 2014 1 commit
  29. 18 Jul, 2013 1 commit
  30. 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.
  31. 14 Feb, 2013 1 commit
  32. 11 Feb, 2013 1 commit