- 13 Oct, 2016 1 commit
-
-
Paco Guzman authored
-
- 11 Oct, 2016 3 commits
-
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
Douglas Barbosa Alexandre authored
-
- 10 Oct, 2016 1 commit
-
-
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.
-
- 07 Oct, 2016 1 commit
-
-
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.
-
- 05 Oct, 2016 1 commit
-
-
James Lopez authored
-
- 04 Oct, 2016 1 commit
-
-
Yorick Peterse authored
Having many system notes isn't really an indication of a project being trending. Including these notes would lead to projects with lots of commit cross references (for example) showing up in the trending projects list.
-
- 28 Sep, 2016 1 commit
-
-
Rémy Coutable authored
Changes include: - Ensure Member.add_user is not called directly when not necessary - New GroupMember.add_users_to_group to have the same abstraction level as for Project - Refactor Member.add_user to take a source instead of an array of members - Fix Rubocop offenses - Always use Project#add_user instead of project.team.add_user - Factorize users addition as members in Member.add_users_to_source - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects - Destroy any requester before adding them as a member - Improve the way we handle access requesters in Member.add_user Instead of removing the requester and creating a new member, we now simply accepts their access request. This way, they will receive a "access request granted" email. - Fix error that was previously silently ignored - Stop raising when access level is invalid in Member, let Rails validation do their work Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 22 Sep, 2016 3 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 21 Sep, 2016 3 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- For target project show only environments for target branch or with tags - For source project show only environments for source branch
-
- 15 Sep, 2016 2 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
Groups can enable/disable LFS, but this setting can be overridden at the project level. Admin only
-
- 14 Sep, 2016 1 commit
-
- 13 Sep, 2016 2 commits
-
-
Yorick Peterse authored
This moves tracking of the pushes since the last Git GC from PostgreSQL to Redis. This reduces the number of writes on the "projects" table. This in turn reduces the vacuuming overhead. The lease used for incrementing the counter has been removed. This lease was mostly put in place to prevent high database load but this isn't needed anymore due to the counter now being stored in Redis. Fixes gitlab-org/gitlab-ce#22125
-
Kamil Trzcinski authored
Use a permissions of user to access all dependent projects from CI jobs (this also includes a container images, and in future LFS files)
-
- 06 Sep, 2016 1 commit
-
-
Connor Shea authored
-
- 01 Sep, 2016 1 commit
-
-
Felipe Artur authored
-
- 31 Aug, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 30 Aug, 2016 3 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
-
Patricio Cano authored
-
- 26 Aug, 2016 1 commit
-
-
Alejandro Rodríguez authored
-
- 25 Aug, 2016 1 commit
-
-
Hannes Rosenögger authored
This commit makes sure that the project icon is being read from the default branch instead of 'master'
-
- 24 Aug, 2016 1 commit
-
-
Douglas Barbosa Alexandre authored
-
- 20 Aug, 2016 1 commit
-
-
Douwe Maan authored
-
- 19 Aug, 2016 1 commit
-
- 18 Aug, 2016 1 commit
-
-
Sean McGivern authored
-
- 17 Aug, 2016 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Paco Guzman authored
Use just SQL to check is a user can admin_issue on a project Tradeoff - we duplicate how we check admin_issue in a SQL relation in the Ability class
-
- 11 Aug, 2016 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 10 Aug, 2016 2 commits
-
-
Rémy Coutable authored
Also, mutualize AccessRequests and Members endpoints for Group & Project. New API documentation for the AccessRequests endpoints. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Stan Hu authored
Instead of redirecting from the project service to the service and back to the model, put all destruction code in the service. Also removes a possible source of failure where run_after_commit may not destroy the project.
-