BigW Consortium Gitlab

  1. 12 Dec, 2016 1 commit
  2. 09 Dec, 2016 1 commit
  3. 01 Dec, 2016 3 commits
  4. 28 Nov, 2016 1 commit
    • Add new configuration setting to enable/disable HTML emails. · b62e2bed
      Ruben Davila authored
      This new global setting will allow admins to specify if HTML emails should be sent or not,
      this is basically useful when system administrators want to save some disk space by avoiding
      emails in HTML format and using only the Plain Text version.
  5. 18 Nov, 2016 1 commit
  6. 14 Nov, 2016 1 commit
  7. 11 Nov, 2016 2 commits
    • Centralize LDAP config/filter logic · c50b98da
      Drew Blessing authored
      Centralize all LDAP config logic in `GitLab::LDAP::Config`. Previously,
      some logic was in the Devise initializer and it was not honoring the
      `user_filter`. If a user outside the configured `user_filter` signed
      in, an account would be created but they would then be denied access.
      Now that logic is centralized, the filter is honored and users outside
      the filter are never created.
  8. 10 Nov, 2016 3 commits
  9. 07 Nov, 2016 1 commit
  10. 04 Nov, 2016 1 commit
    • Set default Sidekiq retries to 3 · d498ec98
      Drew Blessing authored
      By default, Sidekiq will retry 25 times with an exponential backoff.
      This may result in jobs retrying for up to 21 days. Most Sidekiq
      failures occur when attempting to connect to external services -
      Project service hooks, web hooks, mailers, mirror updates, etc.
      We should set a default retry of 3, and if that's not sufficient
      individual workers can override this in the worker class.
  11. 01 Nov, 2016 1 commit
    • Initialize Sidekiq with the list of queues used by GitLab · cde3963d
      Stan Hu authored
      The Sidekiq client API adds an entry to the Sidekiq "queues" list,
      but mail_room and gitlab-shell use redis-rb directly to insert jobs
      into Redis and thus do not make an extra "sadd" call to Redis
      each time a job is inserted. To make it possible to monitor
      these queues via the API, add an initialization step to
      set up the list at startup.
      
      Closes gitlab-com/infrastructure#682
  12. 31 Oct, 2016 1 commit
    • Support for post deployment migrations · 83c82411
      Yorick Peterse authored
      These are regular Rails migrations that are executed by default. A user
      can opt-out of these migrations by setting an environment variable
      during the deployment process.
      
      Fixes gitlab-org/gitlab-ce#22133
  13. 28 Oct, 2016 1 commit
  14. 13 Oct, 2016 1 commit
  15. 10 Oct, 2016 1 commit
    • Precalculate trending projects · 237c8f66
      Yorick Peterse authored
      This commit introduces a Sidekiq worker that precalculates the list of
      trending projects on a daily basis. The resulting set is stored in a
      database table that is then queried by Project.trending.
      
      This setup means that Unicorn workers no longer _may_ have to calculate
      the list of trending projects. Furthermore it supports filtering without
      any complex caching mechanisms.
      
      The data in the "trending_projects" table is inserted in the same order
      as the project ranking. This means that getting the projects in the
      correct order is simply a matter of:
      
          SELECT projects.*
          FROM projects
          INNER JOIN trending_projects ON trending_projects.project_id = projects.id
          ORDER BY trending_projects.id ASC;
      
      Such a query will only take a few milliseconds at most (as measured on
      GitLab.com), opposed to a few seconds for the query used for calculating
      the project ranks.
      
      The migration in this commit does not require downtime and takes care of
      populating an initial list of trending projects.
  16. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.
  17. 06 Oct, 2016 2 commits
  18. 04 Oct, 2016 1 commit
  19. 03 Oct, 2016 1 commit
  20. 30 Sep, 2016 2 commits
  21. 28 Sep, 2016 1 commit
  22. 13 Sep, 2016 1 commit
  23. 12 Sep, 2016 1 commit
  24. 11 Sep, 2016 1 commit
  25. 07 Sep, 2016 2 commits
    • Limited amount of pruned Event rows per run · c0a92cb8
      Olaf Tomalka authored
      Old deployments of Gitlab might have a big number of old events to be
      deleted. Such numbers cause the worker to timeout.
      I've limited the amount of rows that should be destroyed at once to
      10000, and increased how often pruning shall take place to 4 times a
      day.
    • Added cron to prune events older than 12 months. · e25b48ff
      Olaf Tomalka authored
      Since contribution calendar shows only 12 months of activity,
      events older than that time are not visible anywhere and can be
      safely pruned saving big amount of database storage.
      
      Fixes #21164
  26. 06 Sep, 2016 1 commit
  27. 05 Sep, 2016 1 commit
  28. 26 Aug, 2016 1 commit
  29. 25 Aug, 2016 1 commit
  30. 22 Aug, 2016 1 commit
  31. 19 Aug, 2016 1 commit
  32. 18 Aug, 2016 1 commit