BigW Consortium Gitlab

  1. 01 Sep, 2017 1 commit
  2. 27 Jul, 2017 3 commits
  3. 13 Jul, 2017 1 commit
    • Fixes needed when GitLab sign-in is not enabled · 672a68d3
      Robin Bobbitt authored
      When sign-in is disabled:
       - skip password expiration checks
       - prevent password reset requests
       - don’t show Password tab in User Settings
       - don’t allow login with username/password for Git over HTTP requests
       - render 404 on requests to Profiles::PasswordsController
  4. 25 Jun, 2017 1 commit
  5. 23 Jun, 2017 11 commits
  6. 06 Jun, 2017 1 commit
  7. 05 Jun, 2017 1 commit
    • Create read_registry scope with JWT auth · 0b81b5ac
      Z.J. van de Weg authored
      This is the first commit doing mainly 3 things:
      1. create a new scope and allow users to use it
      2. Have the JWTController respond correctly on this
      3. Updates documentation to suggest usage of PATs
      
      There is one gotcha, there will be no support for impersonation tokens, as this
      seems not needed.
      
      Fixes gitlab-org/gitlab-ce#19219
  8. 10 May, 2017 1 commit
  9. 06 Apr, 2017 3 commits
  10. 31 Mar, 2017 1 commit
  11. 17 Mar, 2017 1 commit
  12. 15 Mar, 2017 1 commit
  13. 07 Mar, 2017 1 commit
  14. 06 Mar, 2017 1 commit
  15. 03 Mar, 2017 1 commit
  16. 01 Mar, 2017 1 commit
  17. 28 Feb, 2017 1 commit
  18. 23 Feb, 2017 1 commit
  19. 21 Feb, 2017 1 commit
  20. 15 Feb, 2017 1 commit
  21. 01 Feb, 2017 1 commit
  22. 16 Dec, 2016 2 commits
  23. 23 Nov, 2016 1 commit
    • Remove event caching code · 5371da34
      Yorick Peterse authored
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
  24. 17 Nov, 2016 2 commits