BigW Consortium Gitlab

  1. 14 Apr, 2016 2 commits
  2. 12 Apr, 2016 1 commit
  3. 31 Mar, 2016 1 commit
  4. 17 Mar, 2016 1 commit
  5. 10 Mar, 2016 1 commit
  6. 08 Feb, 2016 1 commit
  7. 02 Feb, 2016 1 commit
  8. 28 Jan, 2016 2 commits
  9. 26 Jan, 2016 1 commit
    • Ensure rake tasks that don't need a DB connection can be run without one · e6f3fe5d
      Rémy Coutable authored
      When using ActiveRecord::Base.connection.active? without a DB
      connection, we get a "PG::ConnectionBad: could not connect to server"
      error because ActiveRecord::Base.connection doesn't exist. By using
      ActiveRecord::Base.connected? we ensure we don't get this error if
      the connection is missing, which is the all point of the
      Gitlab::CurrentSettings#connect_to_db? method!
  10. 25 Jan, 2016 1 commit
  11. 19 Jan, 2016 1 commit
  12. 08 Jan, 2016 1 commit
  13. 30 Dec, 2015 1 commit
  14. 23 Nov, 2015 1 commit
  15. 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
  16. 05 Nov, 2015 1 commit
  17. 01 Sep, 2015 1 commit
  18. 28 Aug, 2015 1 commit
  19. 20 Aug, 2015 1 commit
  20. 11 Jun, 2015 1 commit
  21. 05 Jun, 2015 1 commit
  22. 02 Apr, 2015 1 commit
  23. 07 Mar, 2015 1 commit
  24. 18 Feb, 2015 1 commit
  25. 25 Jan, 2015 3 commits
  26. 15 Jan, 2015 1 commit
  27. 14 Jan, 2015 1 commit
  28. 09 Jan, 2015 1 commit
    • Rescue missing database errors · bc95576e
      Jacob Vosmaer authored
      While loading the Rails app we cannot assume that the gitlabhq_xxx
      database exists already. If we do, `rake gitlab:setup` breaks!
      
      This is a quick hack to make sure that fresh development setups of
      GitLab (from master) will work again.
  29. 08 Jan, 2015 3 commits