- 05 Oct, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
-
- 02 Oct, 2017 2 commits
-
-
Douglas Barbosa Alexandre authored
-
Stan Hu authored
Because of a change in GitLab 9.5.4 to prevent users from assuming control of a repository already on disk, the import task broke. Imports would fail with the message, "There is already a repository with that name on disk". This change skips the validation when the import is done from the command-line. Closes #37682
-
- 29 Sep, 2017 3 commits
-
-
Valery Sizov authored
-
Jacob Vosmaer authored
-
Valery Sizov authored
-
- 28 Sep, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 20 Sep, 2017 2 commits
-
-
Valery Sizov authored
-
Valery Sizov authored
-
- 15 Sep, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
Updating didn't work, as the project_id was missing to be set for the project_auto_devops model. Fixes gitlab-org/gitlab-ce#37893
-
- 14 Sep, 2017 1 commit
-
-
Yorick Peterse authored
This adds Project#latest_successful_pipeline_for and Project#latest_successful_pipeline_for_default_branch. The 2nd method memoizes the result (taking nil values into account) to ensure the underlying query isn't executed multiple times when viewing a project's homepage. See https://gitlab.com/gitlab-org/gitlab-ce/issues/36878#note_40073607 for more information.
-
- 12 Sep, 2017 1 commit
-
-
Felipe Artur authored
-
- 07 Sep, 2017 1 commit
-
-
Kamil Trzcinski authored
-
- 06 Sep, 2017 7 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Zeger-Jan van de Weg authored
-
Ashley Dumaine authored
-
Ashley Dumaine authored
-
Zeger-Jan van de Weg authored
-
- 05 Sep, 2017 1 commit
-
-
Rubén Dávila authored
The following optimizations were performed: - Add new association to GroupMember and ProjectMember This new association will allow us to check if a user is a member of a Project or Group through a single query instead of two. - Optimize retrieving of Members when adding multiple Users
-
- 04 Sep, 2017 3 commits
-
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
-
- 31 Aug, 2017 4 commits
-
-
Zeger-Jan van de Weg authored
-
Zeger-Jan van de Weg authored
Behind an application setting, which defaults to false, this commit implements the implied CI/CD config. Which means that in the case we can't find the `.gitlab-ci.yml` on the commit we want to start a pipeline for, we fall back to an implied configuration. For now the Bash template has been copied to `Auto-Devops.gitlab-ci.yml` so the tests actually work. Fixes #34777
-
Sean McGivern authored
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
-
Zeger-Jan van de Weg authored
In this instance its subgroups, and given we can't deploy it, we shouldn't allow it to be shown. Fixes gitlab-org/gitlab-ce#34864
-
- 30 Aug, 2017 1 commit
-
-
Mike Greiling authored
-
- 29 Aug, 2017 1 commit
-
-
Rubén Dávila authored
-
- 28 Aug, 2017 1 commit
-
-
Felipe Artur authored
-
- 25 Aug, 2017 2 commits
-
-
Gabriel Mazetto authored
There are some redundancies in the validation steps, and that is to preserve current error messages behavior Also few specs have to be changed in order to fix madness in validation logic.
-
Lin Jen-Shin authored
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13766 * Rename AfterImportService * Use constants * Move Git operations to Gitlab::Git::Repository * Use Regexp.union
-
- 24 Aug, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Mehdi Lahmam authored
Closes #35994
-
- 23 Aug, 2017 2 commits
-
-
Lin Jen-Shin authored
Because we don't need them, and they would slow down the repository, keeping unneeded objects as well. We could also consider doing this in regular housekeeping.
-
Yorick Peterse authored
Every project page displays a navigation menu that in turn displays the number of open issues and merge requests. This means that for every project page we run two COUNT(*) queries, each taking up roughly 30 milliseconds on GitLab.com. By caching these numbers and refreshing them whenever necessary we can reduce loading times of all these pages by up to roughly 60 milliseconds. The number of open issues does not include confidential issues. This is a trade-off to keep the code simple and to ensure refreshing the data only needs 2 COUNT(*) queries instead of 3. A downside is that if a project only has 5 confidential issues the counter will be set to 0. Because we now have 3 similar counting service classes the code previously used in Projects::ForksCountService has mostly been moved to Projects::CountService, which in turn is reused by the various service classes. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36622
-
- 22 Aug, 2017 3 commits
-
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-