Co-authored-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>

The `bin/diagnostic-reports-uploader starts successfully` test has the `flakiness::1` label set, which means it has more than 1000 flakiness reports.

This MR quarantines the test. This is a discussion starting point to let the responsible group know about the flakiness
so that they can take action:

- accept the merge request and schedule to improve the test
- close the merge request in favor of another merge request to delete the test

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/448411.

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::QuarantineFlakyTests keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

Deprecated in https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2760
in favor of the new `concurrency` option.

Changelog: removed

This reverts merge request !149690

Deprecated in https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2760
in favor of the new `concurrency` option.

Changelog: removed

Removal of queue selector and negate options for 17.0

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/149370

Changelog: removed

This MR lays groundwork for chosen relation import
(https://gitlab.com/gitlab-org/gitlab/-/issues/425798) by updating
the relation tree restorer to allow importing of a single relation.

It also adds a service and class which will be called by an API endpoint
in a follow-up MR.

Changelog: changed

When routing rules is not specified, all jobs go to `default` and
`mailers` queue by default. We can safely override
sidekiq queue_groups to default,mailers queues only so that Redis don't
incur overhead of BRPOPing 600+ queues.

Changelog: changed

The new concurrency option is a fixed value that doesnt depend on the
queues length. It is means to be a simple replacement over the
min-concurrency and max-concurrency.
https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/2760

Changelog: added

Changelog: other

This moves two spec helpers into `gitlab-rspec`.

Update development guidelines accordingly.

- spec/[b-f]*/**/*.rb

Changelog: other

This system was never in productive use and not
officially supported. We are retiring it now.

See https://gitlab.com/gitlab-org/gitlab-metrics-exporter/-/issues/31

Add migration to remove workers from queue

Update sidekiq queues yml

Changelog: removed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124430

Update default initializer value for Sidekiq routing_rules

See merge request gitlab-org/gitlab!97908

- For better backward compatibility use string keys on
  GitlabSettings::Options
- Remove all the Settingslogic references from code (not comments)
- Ensure to use GitlabSettings::Options when pushing new options to
  Array values
- Instead of inheriting from Hash, wrap a hash in
  GitlabSettings::Options and make it respond to all the requirements.
    * PROS: This provides more autonomy on what needs to be done
    * CONS: Some places were checking by Hash, we need to tackle these
    scenarios
- Ensure to deep_merge return nested Options
- Use the _raw_ version of options when passing to Fog::Storage
- Ensure to load required active_support libraries
- Show the option name in the GitlabSettings::MissingSetting error
- Ensure to have an option `source` for the path of the `gitlab.yml`
- Fix GitlabSettings::Options#deep_merge and
  GitlabSettings::Options#merge to return a new GitlabSettings::Options
  object with the options deep_merged/merged
- Add GitlabSettings#reload! for backward compatibility
- Make file/namespace initializer arguments
- Avoid mutating Settings in sidekiq_cluster/cli tests
- Fix configuration stubbing

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/286873

Changelog: other

There were an additional number of specs failing
that passed once spec_helper was required instead
of fast_spec_helper

Changelog: fixed

We want both processes here to listen to queues, so pick a fairly
lightly-used feature category with few queues to replace the missing
`chatops` category.

Avoid using `[]` notation, use `.`.

sidekiq-cluster handles process supervision for its child Sidekiq
processes, and terminates itself and all child processes if any child
Sidekiq process exits.

Previously, it always exited with a 0 status code (i.e. success), no
matter how the child process had terminated.

Now it exits with 1 if any child process had a non-zero exit code. This
allows a process supervisor one level up (like systemd) to detect
failures and restart.

Changelog: changed

The previous default of 50 was far too high. We don't use this on
GitLab.com and it's mostly inertia that has left it at this value.

Changelog: changed

This change is part of series of changes that will allow projects to
be exported using multiple jobs

Changelog: other

Add the binary and the logic for GCS uploads.

Changelog: other

- Creates a new service that exports project relations separately and
stores the exported relation files in object-store.
- Creates a worker to trigger the generation of the export relation
in the background.

Only `feature_category` was correctly inherited, in addition to
`sidekiq_options` which comes from Sidekiq.

For the other attributes, we need to switch to `get_class_attribute`
in order to also lookup values on parents.

Changelog: changed

Fixed:
- Do not determine `alive` status from the pidset returned
  by caller, since this can lead to "bouncing" state.
- Swap loop-check with sleep call, since sleep suspends
  the calling thread, which may lead to the callback
  being invoked if `alive` is invalidated by another
  thread.
- Do not trap INT and TERM by default; this was swallowing
  these signals for the Puma master.

Changelog: fixed

It has been a long-standing issue that for Sidekiq,
serving metrics and health-checks was coupled into
a single server.

We had already separated settings keys for these two
concerns previously, in anticipation of splitting
these endpoints apart, which is a breaking change.

We can now do this with 15.0.

Changelog: changed

This change:

- Adds a rake task to install gitlab-metrics-exporter
  into a given directory.
- Allows to run it in place of the existing Ruby based
  exporters; this is guarded by an environment variable.
- Extends the existing end-to-end test to test both
  Ruby and Go implementations.

There was a slight chance that the metrics directory got
wiped after workers had started up, which would result
in their metrics missing.

We were accidentally deleting metrics the exporter
server exported about itself. Actual sidekiq worker
metrics were not affected.

This happened because we would wipe the metrics dir
whenever sidekiq_0 starts up, but this happens after
the metrics server starts, so the worker was deleting
those existing metrics.

Changelog: fixed

This moves us away from a process-internal server thread
and toward an external process that we supervise instead.

This extracts the process supervision logic
from sidekiq-cluster into a helper module.

We will re-use this for Puma soon.

This provides better memory use for Puma, and we
will require this for running a non-Ruby server
in the future.

This does not actually start the server for Puma
yet.