| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Show a list of obsolete `ignored_columns`
|
|
|
|
This class encapsulates our use of the Danger gem.
|
|
This reverts merge request !32196
|
|
The benefit of running the danger_local Rake task
is that it displays some informational messages
for clarity and also exits with 1 if there's any
output.
|
|
Add direct upload support for personal snippets
See merge request gitlab/gitlabhq!3226
|
|
Remove the visual review toolbar code
in favor of using the NPM package.
|
|
|
|
Migrate legacy uploads rake tasks
See merge request gitlab-org/gitlab-ce!29409
|
|
- move uploads created by AttachmentUploader
- handle also files created for legacy_diff_notes
|
|
As per https://gitlab.com/gitlab-org/gitlab-ce/issues/46043, project
templates should be squashed before updating, so that repositories
created from these templates don't include the full history of the
backing repository.
|
|
|
|
This rake task had been broken for a while. This fixes the breakages,
adds a test to help avoid future breakages, and adds a few ergonomic
improvements to the task itself.
|
|
Backport EE changes made to the scripts/ directory
See merge request gitlab-org/gitlab-ce!31015
|
|
This backport changes made by EE to the files in the scripts/ directory.
This comes with a few changes to some scripts to make them work in the
single codebase setup.
|
|
We dropped MySQL support and a lot of mysql specific code has been
removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608.
This comes in from the other direction and removes any `if postgresql?`
branches.
|
|
Changes all calls to data_source_exists? to table_exists?
since that is the intent of these calls
|
|
Resolves confusion within spec rake tasks.
See merge request gitlab-org/gitlab-ce!31073
|
|
|
|
None of this code can be reached any more, so it can all be removed
|
|
In some cases ActiveSession.cleanup was not called after authentication,
so for some user ActiveSession lookup keys grew without ever cleaning
up. This Rake task manually iterates over the lookup keys and removes
ones without existing ActiveSession.
|
|
Moves every fixture source file from
spec/javascripts to spec/frontend
|
|
Introduces frontend:fixtures rake task to replace
karma:fixtures and update documentation and CI scripts
to match
|
|
Add unset_rugged rake task
Closes #64441
See merge request gitlab-org/gitlab-ce!30636
|
|
to specify backfill_weeks and average_issues_per_week
|
|
Display the amount for Hashed Storage migration/rollback correctly
Closes #63667
See merge request gitlab-org/gitlab-ce!29996
|
|
Adds an unset_rugged rake task that unsets all rugged feature flags.
Also fixes the existing disable_rugged task to have it explicitly
disable feature flags instead of just unsetting them.
|
|
Adds more friendly docs for GraphQl implementation
|
|
Rake script considers the specified range, if present, to calculate
the affected amount of projects correctly.
|
|
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
|
|
|
|
|
Add rake task to clean orphan artifact files
See merge request gitlab-org/gitlab-ce!29681
|
|
This adds the rake task rake
gitlab:cleanup:orphan_job_artifact_files. This rake task cleans all
orphan job artifact files it can find on disk.
It performs a search on the complete folder of all artifacts on
disk. Then it filters out all the job artifact ID for which it could
not find a record with matching ID in the database. For these, the
file is deleted from disk.
|
|
Fixed some spelling
Dropped rake task description for a prefix only task
Added note on skipping the check to the postgres debugging dev doc
|
|
We no longer need to point people away from using db:migrate
|
|
If you chose to use the rollback migration feature on your current
version for example, you should still have a way to migrate, being
that you are still on a supported migration path.
|
|
|
|
Rather than have it checked only as part of gitlab:db:configure, we will
instead have it as a pre-req for every db:migrate command
|
|
Set the mininum supported migration version to be the schema version as
of 11.11.0, and errors you if that is not detected during
gitlab:db:configure
|
|
If CRON=1 is in use, we shouldn't generate any output or admins may be
notified via e-mail about unnecessary warnings.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63703
|
|
This backports all EE schema changes to CE, including EE migrations,
ensuring both use the same schema.
== Updated tests
A spec related to ghost and support bot users had to be modified to make
it pass. The spec in question assumes that the "support_bot" column
exists when defining the spec. In the single codebase setup this is not
the case, as the column is backported in a later migration. Any attempt
to use a different schema version or use of "around" blocks to
conditionally disable specs won't help, as reverting the backport
migration would also drop the "support_bot" column. Removing the
"support_bot" tests entirely appears to be the only solution.
We also need to update some foreign key tests now that we have
backported the EE columns. Fortunately, these changes are very minor.
== Backporting migrations
This commit moves EE specific migrations (except those for the Geo
tracking database) and related files to CE, and also removes any traces
of the ee/db directory.
Some migrations had to be modified or removed, as they no longer work
with the schema being backported. These migrations were all quite old,
so we opted for removing them where modifying them would take too much
time and effort.
Some old migrations were modified in EE, while also existing in CE. In
these cases we took the EE code, and in one case removed them entirely.
It's not worth spending time trying to merge these changes somehow as we
plan to remove old migrations around the release of 12.0, see
https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
|
|
|
|
Upgrade Gitaly to v1.43.0
See merge request gitlab-org/gitlab-ce!28867
|
|
It used to be the case that GitLab created symlinks for each repository
to one copy of the Git hooks, so these ran when required. This changed
to set the hooks dynamically on Gitaly when invoking Git.
The side effect is that we didn't need all these symlinks anymore, which
Gitaly doesn't create anymore either. Now that means that the tests in
GitLab-Rails should test for it either.
Related: https://gitlab.com/gitlab-org/gitaly/issues/1392#note_175619926
|
|
It takes a lot of lines to move a script
|
|
This reverts commit 744f1f2e7037f5c70c3168d9e2e89b1c327465d2, reversing
changes made to c4d930e5f54e7da07c80cc028dfc0f5c08719146.
|
|
This reverts merge request !27514
|
|
Reorganize test jobs by level
See merge request gitlab-org/gitlab-ce!27514
|
