BigW Consortium Gitlab

  1. 09 Mar, 2017 4 commits
  2. 07 Mar, 2017 1 commit
  3. 28 Feb, 2017 1 commit
  4. 24 Feb, 2017 1 commit
    • Don't allow deleting a ghost user. · 6fdb17cb
      Timothy Andrew authored
      - Add a `destroy_user` ability. This didn't exist before, and was implicit in
        other abilities (only admins could access the admin area, so only they could
        destroy all users; a user can only access their own account page, and so can
        destroy only themselves).
      
      - Grant this ability to admins, and when the current user is trying to destroy
        themselves. Disallow destroying ghost users in all cases.
      
      - Modify the `Users::DestroyService` to check this ability. Also check it in
        views to decide whether or not to show the "Delete User" button.
      
      - Add a short summary of the Ghost User to the bio.
  5. 23 Feb, 2017 1 commit
  6. 05 Feb, 2017 1 commit
  7. 31 Jan, 2017 3 commits
    • Fix pages abilities · 3e6cbcdd
      Kamil Trzcinski authored
    • Initial work on GitLab Pages update · 5f7257c2
      Kamil Trzcinski authored
    • Add GitLab Pages · 120f9aba
      Kamil Trzcinski authored
      - The pages are created when build artifacts for `pages` job are uploaded
      - Pages serve the content under: http://group.pages.domain.com/project
      - Pages can be used to serve the group page, special project named as host: group.pages.domain.com
      - User can provide own 403 and 404 error pages by creating 403.html and 404.html in group page project
      - Pages can be explicitly removed from the project by clicking Remove Pages in Project Settings
      - The size of pages is limited by Application Setting: max pages size, which limits the maximum size of unpacked archive (default: 100MB)
      - The public/ is extracted from artifacts and content is served as static pages
      - Pages asynchronous worker use `dd` to limit the unpacked tar size
      - Pages needs to be explicitly enabled and domain needs to be specified in gitlab.yml
      - Pages are part of backups
      - Pages notify the deployment status using Commit Status API
      - Pages use a new sidekiq queue: pages
      - Pages use a separate nginx config which needs to be explicitly added
  8. 23 Jan, 2017 1 commit
  9. 18 Jan, 2017 2 commits
  10. 29 Dec, 2016 1 commit
  11. 26 Dec, 2016 1 commit
  12. 16 Dec, 2016 1 commit
  13. 13 Dec, 2016 1 commit
  14. 04 Dec, 2016 2 commits
  15. 01 Dec, 2016 1 commit
  16. 30 Nov, 2016 1 commit
  17. 09 Nov, 2016 1 commit
  18. 07 Nov, 2016 2 commits
    • Process commits in a separate worker · 509910b8
      Yorick Peterse authored
      This moves the code used for processing commits from GitPushService to
      its own Sidekiq worker: ProcessCommitWorker.
      
      Using a Sidekiq worker allows us to process multiple commits in
      parallel. This in turn will lead to issues being closed faster and cross
      references being created faster. Furthermore by isolating this code into
      a separate class it's easier to test and maintain the code.
      
      The new worker also ensures it can efficiently check which issues can be
      closed, without having to run numerous SQL queries for every issue.
    • Added IssueCollection · f694f94c
      Yorick Peterse authored
      This class can be used to reduce a list of issues down to a subset based
      on user permissions. This class operates in such a way that it can
      reduce issues using as few queries as possible, if any at all.
  19. 01 Nov, 2016 1 commit
  20. 21 Oct, 2016 1 commit
  21. 19 Oct, 2016 4 commits
  22. 17 Oct, 2016 1 commit
  23. 11 Oct, 2016 1 commit
  24. 06 Oct, 2016 1 commit
  25. 20 Sep, 2016 1 commit
  26. 16 Sep, 2016 1 commit
  27. 15 Sep, 2016 1 commit
  28. 13 Sep, 2016 1 commit
  29. 08 Sep, 2016 1 commit