- 11 Sep, 2018 2 commits
-
-
Fatih Acet authored
-
James Lopez authored
-
- 10 Sep, 2018 5 commits
-
-
Douglas Barbosa Alexandre authored
-
James Lopez authored
-
Rémy Coutable authored
This port https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7254 to CE. Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by:
Rémy Coutable <remy@rymai.me>
-
Tim Zallmann authored
-
- 09 Sep, 2018 3 commits
-
-
Stan Hu authored
This is similar to https://gitlab.com/gitlab-org/gitlab-ee/issues/7511, but the root cause is https://gitlab.com/gitlab-org/gitlab-ce/issues/51268.
-
Stan Hu authored
This is similar to https://gitlab.com/gitlab-org/gitlab-ee/issues/7511, but the root cause is https://gitlab.com/gitlab-org/gitlab-ce/issues/51268.
-
Eva Kadlecová authored
-
- 08 Sep, 2018 4 commits
-
-
Stan Hu authored
If one spec disables the usage ping in the in-memory application settings (e.g. spec/features/usage_stats_consent_spec.rb), then this spec will fail. To work around this problem, we enable the usage ping explicitly in the setup phase. Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7290
-
André Luís authored
-
Martin Wortschack authored
-
Brett Walker authored
-
- 07 Sep, 2018 26 commits
-
-
Dennis Tang authored
The check for the "Invite member" tab for the test where a project cannot be shared with groups isn't relevant, and needs to be removed since in EE the visibility rules for the tab are different due to both the group and membership lock capabilities.
-
Clement Ho authored
-
Stan Hu authored
When a container registry has many tags, it's easy for the DELETE call to take more than 60 seconds and fail. This can also leave the registry in a bad state with null bytes since some of the images have been deleted with tags still pointing to them. In addition, we have to prevent users from accidentally initiating the delete multiple times or this could leave the registry with orphaned tags. This commit also adds a flash message to notify the user the registry is scheduled for deletion. Closes #49926, #51063
-
Rubén Dávila authored
If user has configure the setting then it will be passed to gitlab-shell and gitlab-workhorse
-
Jan Provaznik authored
Labels are sorted by reference, not title. This caused random CI failure.
-
Tim Zallmann authored
-
George Tsiolis authored
-
Stan Hu authored
On GitLab.com, there are over 2 million orphaned label links out of a total of 13 million. These orphaned label links can cause quiet failures, such as unexpected nil values in ExportCsvWorker. Closes gitlab-org/gitlab-ee#7482
-
Jan Provaznik authored
-
Brett Walker authored
-
Tim Zallmann authored
-
Francisco Javier López authored
-
James Lopez authored
-
Jan Provaznik authored
-
Oswaldo Ferreira authored
-
James Lopez authored
-
Zeger-Jan van de Weg authored
Rake tasks cleaning up the Git storage were still using direct disk access, which won't work if these aren't attached. To mitigate a migration issue was created. To port gitlab:cleanup:dirs, and gitlab:cleanup:repos, a new RPC was required, ListDirectories. This was implemented in Gitaly, through https://gitlab.com/gitlab-org/gitaly/merge_requests/868. To be able to use the new RPC the Gitaly server was bumped to v0.120. This is an RPC that will not use feature gates, as this doesn't scale on .com so there is no way to test it at scale. Futhermore, we _know_ it doesn't scale, but this might be a useful task for smaller instances. Lastly, the tests are slightly updated to also work when the disk isn't attached. Eventhough this is not planned, it was very little effort and thus I applied the boy scout rule. Closes https://gitlab.com/gitlab-org/gitaly/issues/954 Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40529
-
Douglas Barbosa Alexandre authored
-
James Lopez authored
-
Phil Hughes authored
-
Phil Hughes authored
-
Phil Hughes authored
-
Phil Hughes authored
-
Tim Zallmann authored
-
Tim Zallmann authored
-
Tim Zallmann authored
-