GitLab

Also removes unnecessary methods causing extra queries

`allow_local_requests_for_hooks_and_services` was renamed to
`allow_local_requests_for_web_hooks_and_services`.

Simplify SystemHookUrlValidator to inherit from PublicUrlValidator
Refactor specs to move out shared examples to be used in both
system hooks and public url validators.

This MR adds new application setting to network section
`allow_local_requests_from_system_hooks`. Prior to this change
system hooks were allowed to do local network requests by default
and we are adding an ability for admins to control it.

CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14520

Introducing Docker Registry replication

This implements the support for `needs:` keyword
as part of GitLab CI. That makes some of the jobs
to be run out of order.

For customers with thousands of entries in the table, lookups for an
LDAP identity dominated the PostgreSQL statistics because of sequential
scans. We can speed this up by adding a partial index with the
extern_uid and provider.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59630

These migrations do the following:

- Adds a new `issue_id` column to `versions`. This fixes an n+1 problem
  when loading versions for an issue in GraphQL as AR can now load from
  cache
- Change the unique restraint on versions.sha to be scoped to `issue_id`
  as in order to import version data, we need to allow duplicate `sha`
  values for versions
- Update all versions with an `issue_id`

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

Adds Job specific variables to facilitate specifying variables when
running manual jobs.

It needs to default to an empty array logically.

Also adds index to support scopes and queries

This supports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14656

* Limits raw requests to 300 per minute and per raw path.
* Add a new attribute to ApplicationSettings so user can change this
value on their instance.
* Uses Gitlab::ActionRateLimiter to limit the raw requests.
* Add a new method into ActionRateLimiter to log the event into auth.log

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/48717

Signed-off-by: Istvan szalai <istvan.szalai@savoirfairelinux.com>

This is the first part of Docker Registry replication
    for secondary Geo node.

This is no longer needed with Rails 5.2. opclass is the attribute used
per https://github.com/rails/rails/pull/19090/files.

Now that we've removed the monkey patch and restored the Rails schema
dumper, it appears Rails has dropped the inclusion of `using: :btree` as
well (https://github.com/rails/rails/pull/27981).

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64529

Add cr remarks

Improve specs according to the review

Fix schema

Add cr remarks

Fix naming

Add cr remarks

To allow project filtering

Prepare summary for accepting multiple groups

Modify deploys group summary class

Add filtering by project name in issues summary

Fix rubocop offences

Add changelog entry

Change name to id in project filtering

Fix rebase problem

Add project extraction

and state

Adds migration to introduce non-regular rule_types to
approval_project_rules

- Set access level in before_validation hook
- Add post migration for updating existing project_features

- Background migration for changing null values to false
- Set false as default value for private_profile DB column

This eliminates conflicts between CE and EE db/schema.rb files.

This makes the CE and EE tables consistent and ensures changes in the
schema for the CE version don't cause conflicts with EE.

Updates changed method names and fixes spec failures

When GitLab was migrating to Gitaly, feature flags were used. These are
now out of use, and essentially a no-op. But they do make the output of
chatops ugly and the feature table is selected in full by the
application.

This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.

After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.

Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at

This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.

Empty usernames will be saved as null in the database.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.

- Migration updates existing groups to "owner", then sets default to
  "maintainer" so that new groups will default to that
- Update spec examples

- instead of using properties
- backward compatibility has to be kept for now