- 11 Jul, 2017 1 commit
-
-
Paul Charlton authored
-
- 07 Jul, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 06 Jul, 2017 1 commit
-
-
Yorick Peterse authored
This removes the need for relying on Rails' "dependent" option for data removal, which is _incredibly_ slow (even when using :delete_all) when deleting large amounts of data. This also ensures data consistency is enforced on DB level and not on application level (something Rails is really bad at). This commit also includes various migrations to add foreign keys to tables that eventually point to "projects" to ensure no rows get orphaned upon removing a project.
-
- 29 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 27 Jun, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 16 Jun, 2017 1 commit
-
-
Michael Kozono authored
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 12 Jun, 2017 1 commit
-
-
Yorick Peterse authored
Background migrations can be used to perform long running data migrations without these blocking a deployment procedure. See MR https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/11854 for more information.
-
- 05 Jun, 2017 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Tiago Botelho authored
-
- 01 Jun, 2017 1 commit
-
- 31 May, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 25 May, 2017 2 commits
-
-
Felipe Artur authored
-
Alexander Randa authored
* implemented logging of project and system web hooks * implemented UI for user area (project hooks) * implemented UI for admin area (system hooks) * implemented retry of logged webhook * NOT imeplemented log remover
-
- 22 May, 2017 2 commits
-
-
Felipe Artur authored
-
Z.J. van de Weg authored
These were untested by the cherry picked commit.
-
- 18 May, 2017 1 commit
-
-
Toon Claes authored
The ProjectCacheWorker refreshes cache periodically, but it runs outside Rails context. So include the ActionView helpers so the `content_tag` method is available.
-
- 15 May, 2017 2 commits
-
-
Z.J. van de Weg authored
When the owner of a pipelines schedule was either blocked or was removed from the project, the pipeline schedular would still schedule the pipeline. This would than fail however, given the user had no access to the project and it contents. However, a better way to handle it would be to not schedule it at all. Furthermore, from now on, such schedules will be deactivated so the schedule worker can ignore it on the next runs.
-
Lin Jen-Shin authored
-
- 12 May, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 10 May, 2017 3 commits
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Toon Claes authored
Since this is a cleanup, ran by a post-deploy, there is no need to lookup the admin to run the cleanup.
-
Toon Claes authored
Destroying projects can be very time consuming. So instead of destroying them in the post-deploy, just schedule them and make Sidekiq do the hard work. They are scheduled in batches of 5000 records. This way the number of database requests is limited while also the amount data read to memory is limited.
-
- 08 May, 2017 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 07 May, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 05 May, 2017 2 commits
-
-
James Lopez authored
-
Alejandro Rodríguez authored
-
- 04 May, 2017 3 commits
-
-
James Edwards-Jones authored
-
James Lopez authored
-
James Lopez authored
-
- 03 May, 2017 2 commits
-
-
James Lopez authored
-
James Lopez authored
-
- 01 May, 2017 2 commits
-
-
Zeger-Jan van de Weg authored
-
Robert Speicher authored
-
- 26 Apr, 2017 1 commit
-
-
Sean McGivern authored
- Ignore JS fixtures - Ignore qa directory - Rewrite concern specs to put concern name first
-
- 24 Apr, 2017 3 commits
-
-
Toon Claes authored
-
Toon Claes authored
Make it gracefully handle unexisting pipelines and refactor iterating all the merge request paths.
-
Toon Claes authored
And add some specs.
-