- 02 Jul, 2019 40 commits
-
-
Lukas Eipert authored
-
Dmitriy Zaporozhets authored
Squash old migrations Closes #59177 See merge request gitlab-org/gitlab-ce!30226
-
Phil Hughes authored
Merge branch '45104-special-characters-in-project-name-path-prevent-users-from-using-the-container-registry' into 'master' Resolve "Special characters in project name/path prevent users from using the container registry" Closes #62770 and #45104 See merge request gitlab-org/gitlab-ce!29616
-
Nick Kipling authored
Includes changes to the Vue container registry component to support the display of an empty message and error message when invalid characters are found in the group, project or branch name. repositories/index.html.haml has been changed to remove the content and place into Vue component.
-
Dmitriy Zaporozhets authored
Feature/uninstall cluster ingress See merge request gitlab-org/gitlab-ce!29977
-
João Cunha authored
- JupyterHub must not be available (installed or updated)
-
Marin Jankovski authored
Disable juint reports tmp See merge request gitlab-org/gitlab-ce!30254
-
Phil Hughes authored
Resolve "Cannot delete and upload file of the same name in the Web IDE" Closes #60859 See merge request gitlab-org/gitlab-ce!30239
-
Denys Mishunov authored
If an entry has been removed from the tree and later, during the same session, a user is trying to add a new item with the same name/path we should allow for that as long as the original entry is marked with `deleted`.
-
Phil Hughes authored
Removes EE differences for app/views/admin/services/_form.html.haml Closes gitlab-ee#12532 See merge request gitlab-org/gitlab-ce!30231
-
Rémy Coutable authored
Add a memory cache local to the thread to reduce Redis load Closes #63977 See merge request gitlab-org/gitlab-ce!30233
-
Steve Azzopardi authored
The junit reports are creating 90mb files inside of redis for `gitlab-ce/ee` project. There is an ongoing production incident https://gitlab.com/gitlab-com/gl-infra/production/issues/928 that is because of high CPU uitlaization on the redis nodes. GitLab-ce/ee are the highest consumers of memory becuase of these junit reports. This is a bandage until we can scale redis properly.
-
James Lopez authored
Don't show image diff note on text file See merge request gitlab-org/gitlab-ce!30221
-
Achilleas Pipinellis authored
Clarify 10k architecture resource per node Closes #63424 See merge request gitlab-org/gitlab-ce!30237
-
Achilleas Pipinellis authored
Fix most bare URLs in project Closes gitlab-com/gitlab-docs#287 See merge request gitlab-org/gitlab-ce!30240
-
Evan Read authored
Linting rule not enabled for now because tooling produces false positives.
-
Achilleas Pipinellis authored
Docs: update global nav document See merge request gitlab-org/gitlab-ce!30230
-
Marcia Ramos authored
-
Nick Thomas authored
-
Nick Thomas authored
-
Nick Thomas authored
On the assumption that a background migration whose specs need a schema older than 2018 is obsoleted by this migration squash, we can remove both specs and code for those that fail to run in CI as a result of the schema at that date no longer existing. This is true for all but the MigrateStageStatus background migration, which is also used from the MigrateBuildStage background migration.
-
Nick Thomas authored
Since the migrations are gone, we don't need these specs either
-
Nick Thomas authored
-
Nick Thomas authored
Use the `squasher` gem to squash migrations older than the start of 2018
-
Thong Kuah authored
Memoizing root_ancestor in Namespace See merge request gitlab-org/gitlab-ce!30248
-
Adam Hegyi authored
The root_ancestor method is heavily used in EE for the group_saml feature. Having this memoization implemented in CE would eliminate the need of overriding the root_ancestor method in EE.
-
Jan Provaznik authored
Tidy spec for API::ProjectClusters See merge request gitlab-org/gitlab-ce!30154
-
Stan Hu authored
-
Sanad Liaquat authored
QA: transfer project spec See merge request gitlab-org/gitlab-ce!28255
-
Jennifer Louie authored
-
Kushal Pandya authored
Hid re-named entries in subfolders Closes #63984 See merge request gitlab-org/gitlab-ce!30242
-
Stan Hu authored
The introduction of the in-memory cache for application settings had a side effect of making it harder to invalidate changes when the settings occur. We now bypass the cache because it's possible the admin enabled the usage ping, and we don't want to annoy the user again if they already set the value. To avoid causing significant load on the system, we add an extra check to ensure the user is an admin. and we don't want to annoy the user again if they already set the value. This is a bit of hack, but the alternative would be to put in a more complex cache invalidation step. Since this call only gets called in the uncommon situation where the user is an admin and the only user in the instance, this shouldn't cause too much load on the system.
-
Evan Read authored
Add ClusterRole step to external Knative docs See merge request gitlab-org/gitlab-ce!30123
-
Hordur Freyr Yngvason authored
This reverts commit 092542d2fa5c036e4fc01ba3185f1dc0e9ddbebb. Included a stray file
-
Stan Hu authored
The /admin panel will now always return an uncached application setting to ensure it always has the most current info.
-
Stan Hu authored
-
Stan Hu authored
Loading `ApplicationSetting` from Redis was responsible for at least 50% of the CPU load of the Redis cluster on GitLab.com. Since these values generally don't change very much, we can load this from the database and cache it in memory, skipping Redis altogther. We use `ActiveSupport::Cache::MemoryStore` as a drop-in replacement for `RedisCacheStore` even though we probably don't need synchronized access within `Thread.current`. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63977
-
Mike Greiling authored
Vue-i18n: autofix for app/assets/javascripts/clusters directory See merge request gitlab-org/gitlab-ce!29962
-
Ezekiel Kigbo authored
i18n linting for .vue files under the app/assets/javascripts/clusters/ directory
-
Dylan Griffith authored
-