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. 31 May, 2016 1 commit
  3. 25 May, 2016 1 commit
  4. 23 May, 2016 1 commit
  5. 16 May, 2016 1 commit
  6. 08 Feb, 2016 1 commit
  7. 19 Nov, 2015 1 commit
  8. 18 Nov, 2015 2 commits
  9. 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
  10. 03 Nov, 2015 1 commit
  11. 02 Nov, 2015 1 commit
  12. 16 Oct, 2015 1 commit
  13. 06 Oct, 2015 6 commits
  14. 25 Sep, 2015 1 commit
    • Add support for AWS S3 Server-Side Encryption support · 253d2320
      Paul Beattie authored
      This adds support for AWS S3 SSE with S3 managed keys, this means the
      data is encrypted at rest and the encryption is handled transparently to
      the end user as well as in the AWS Console. This is optional and not
      required to make S3 uploads work.
  15. 18 Sep, 2015 1 commit
  16. 15 Sep, 2015 3 commits
  17. 21 Aug, 2015 1 commit
  18. 12 Aug, 2015 1 commit
  19. 30 Jul, 2015 1 commit
  20. 29 Jul, 2015 1 commit
  21. 21 Jul, 2015 1 commit
    • Don't stop if database.sql.gz already exists · 346b0749
      Jacob Vosmaer authored
      The existing behavior of the backups is to overwrite whatever data
      was still there in the scratch directories. This broke when we added
      a 'gzip' step because 'gzip database.sql' will fail if 'database.sql.gz'
      already exists. Doing 'rm -f database.sql.gz' before the 'gzip'
      avoids this failure.
  22. 07 Jul, 2015 1 commit
  23. 06 Jul, 2015 2 commits
  24. 09 Jun, 2015 2 commits
  25. 02 Apr, 2015 1 commit
  26. 28 Mar, 2015 1 commit
    • Don't use chmod_R for backup tars · 0f78d92e
      Vinnie Okada authored
      When creating backup tar files, only change permissions on the `db`,
      `uploads`, and `repositories` directories, not their contents.
  27. 25 Mar, 2015 1 commit
  28. 20 Mar, 2015 1 commit
  29. 19 Mar, 2015 1 commit
  30. 18 Mar, 2015 1 commit