| Age | Commit message (Collapse) | Author |
|---|
|
|
|
These changes make the code more reusable, testable, and most
importantly, overrideable.
|
|
|
|
Rename Repository table to PoolRepository
See merge request gitlab-org/gitlab-ce!23236
|
|
Removes all the irrelevant code and columns that were migrated from the Project…
See merge request gitlab-org/gitlab-ce!21497
|
|
Clears the import related columns and code from the Project
model over to the ProjectImportState model
|
|
To separate the different kinds of repositories we have at GitLab this
table will be renamed to pool_repositories. A project can, for now at
least, be member of none, or one of these. The table will get additional
columns in a later merge request where more logic is implemented for the
model.
Further included is a small refactor of logic around hashing ids for the
disk_path, mainly to ensure a previous implementation is reusable.
The disk_path for the pool_repositories table no longer has a NOT NULL
constraint, but given the hashing of the ID requires the DB to assign
the record an ID, an after_create hook is used to update the value.
A related MR is:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23143, adding
tables for 'normal' repositories and wiki_repositories.
|
|
This approach caused many different problems as we tightened
the query execution timeout.
|
|
Most of these checks are not valuable in the current setup, thus removed
and replaced by Gitaly checking if its read and writeable.
Depends on:
1. https://gitlab.com/gitlab-org/gitaly/merge_requests/675
|
|
Delegate storage health check to Gitaly's health check
Closes gitaly#1336
See merge request gitlab-org/gitlab-ce!22063
|
|
|
|
|
|
|
|
This was used in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16648
and this could happen from time to time, so let's just keep it.
|
|
Also, since Gitaly now takes care of checking for storage paths
existence/accessibility, we can remove those check from the
gitlab:gitlab_shell_check task and advance further into 0 direct disk
approach on gitlab-rails
|
|
|
|
|
|
|
|
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6906
See merge request gitlab-org/gitlab-ce!21903
|
|
We started syncing all the wiki regardless of the fact it's disabled or
not. We couldn't do that in one stage because of needing of smoth update
and deprecating things. This is the second stage that finally removes
unused columns in the geo_node_status table.
|
|
Fast lookup of authorized SSH keys in the database was ported to CE in
v10.4. This change adds the option to enable the setting via the restore
rake task and assumes yes if the force env variable is set.
|
|
See merge request gitlab-org/gitlab-ce!21689
|
|
Add a rake task that will trigger gitlab:uploads:migrate rake task with
different possible arguments, one by one.
|
|
|
|
If doing a schema load, the post_migrations should also be marked as up,
even if SKIP_POST_DEPLOYMENT_MIGRATIONS was set, otherwise future
migration runs will be broken.
|
|
Resolve "Remove old storage logic from Import/Export"
Closes #51144, #50109, #48778, and #51079
See merge request gitlab-org/gitlab-ce!21409
|
|
Port cleanup tasks to use Gitaly
Closes #40529 and gitaly#954
See merge request gitlab-org/gitlab-ce!21588
|
|
|
|
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
|
|
|
|
Updated docs, refactor import/export code
Fix AvatarUploader path issue
Fix project export upload webhook error
|
|
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
|
|
|
|
Remove storage path dependency of gitaly install task
See merge request gitlab-org/gitlab-ce!21101
|
|
|
|
|
|
|
|
While reviewing this branch it was noted that this task was broken.
Given the limited value this task brings, and given the fact that much
of the old behaviour has been moved to be automatically fixed, removing
was a good option.
Suggestion in:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20806#note_91261001
|
|
These tasks are happening through housekeeping right now, by default
ever 10th push. This removes the need for these tasks.
Side note, this removes one of my first contributions to GitLab, as back
than I introduced these tasks through: 54e6c0045bb13c05cc5478cbdf47d3246bd9fe2b
Closes https://gitlab.com/gitlab-org/gitaly/issues/768
|
|
Resolve "Disable SAML and Bitbucket if OmniAuth is disabled"
Closes #48932
See merge request gitlab-org/gitlab-ce!20608
|
|
We also try to unify the way we setup OmniAuth, and how we check
if it's enabled or not.
|
|
Introduced by f20eadcbbeb88e98c2608cbaf23f0d09ca002a98, meant to remove
refs from Git using the wrong name. That never made it to a non-rc
release and can be safely removed now.
|
|
|
|
This will help us avoid conflicts when regenerating the pot file, the
timestamps aren't used by Crowdin.
|
|
|
|
Making the `gettext:updated_check` by completely regenerating the gitlab.pot.
This avoids an issue where `gettext:find` would not pick up on changes
if the file isn't removed first.
|
|
|
