BigW Consortium Gitlab

  1. 21 Jun, 2017 1 commit
  2. 20 Jun, 2017 1 commit
  3. 14 Jun, 2017 1 commit
  4. 24 May, 2017 1 commit
  5. 18 May, 2017 1 commit
  6. 15 May, 2017 1 commit
    • Don't reuse gRPC channels · 43f037c9
      Jacob Vosmaer authored
      It seems that bad things happen when two gRPC stubs share one gRPC
      channel so let's stop doing that. The downside of this is that we
      create more gRPC connections; one per stub.
  7. 12 May, 2017 2 commits
  8. 10 May, 2017 1 commit
  9. 04 May, 2017 1 commit
  10. 01 May, 2017 1 commit
  11. 28 Apr, 2017 1 commit
  12. 26 Apr, 2017 1 commit
  13. 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.
  14. 04 Apr, 2017 1 commit
  15. 29 Mar, 2017 2 commits
  16. 27 Mar, 2017 1 commit
  17. 21 Mar, 2017 3 commits
  18. 03 Mar, 2017 2 commits
  19. 28 Feb, 2017 1 commit
  20. 23 Feb, 2017 4 commits
  21. 07 Feb, 2017 1 commit
  22. 01 Feb, 2017 1 commit
  23. 31 Jan, 2017 1 commit
    • 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
  24. 09 Jan, 2017 1 commit
  25. 16 Dec, 2016 1 commit
    • Add LDAP task to rename a provider · e0eb86ee
      Drew Blessing authored
      Sometimes admins will change the LDAP configuration, not realizing
      that problems will occur if the user's LDAP identities are not
      also updated to use the new provider name. This task will give
      admins a single command to run to update identities and will
      prevent having to run multiple Rails console queries.
  26. 01 Dec, 2016 1 commit
  27. 30 Nov, 2016 4 commits
  28. 08 Nov, 2016 1 commit
  29. 01 Nov, 2016 1 commit