EE: Validate that foreign keys are created

Closes gitlab-ce#50875

See merge request gitlab-org/gitlab-ee!8232

EE: Refactor how a few ActiveRecord enums are defined

See merge request gitlab-org/gitlab-ee!8469

Add saml_discovery_token unauthenticated access

See merge request gitlab-org/gitlab-ee!8016

Fix object storage tier information

See merge request gitlab-org/gitlab-ee!8383

Merge branch '8145-consider-using-something-other-than-a-strike-for-dismissed-vulnerabilities' into 'master'

Restyling the dismissed vulnerabilities

Closes #8145

See merge request gitlab-org/gitlab-ee!8401

This will allow us to determine if the existance of
a private group can be revealed to a user

- use v-show in place of v-if for dismissed states
- wrap custom class name in quotes
- adds tests for the changes

Add e2e test: auto-assign code owners

See merge request gitlab-org/gitlab-ee!8372

# Conflicts:
#   qa/qa/page/merge_request/show.rb

Include classification label in project API

Closes #8399

See merge request gitlab-org/gitlab-ee!8426

CE upstream - 2018-11-15 21:22 UTC

See merge request gitlab-org/gitlab-ee!8476

Disable password autocomplete in mirror form fill

Closes gitlab-ce#50812

See merge request gitlab-org/gitlab-ee!8477

Chrome and other browsers ignore `autocomplete=false` and
`autocomplete=off` now. We suspect that this caused the mirroring
section to expand whenever a user clicked "Expand" in the Repository
settings.

https://developers.google.com/web/fundamentals/design-and-ux/input/forms/?hl=en
recommends using `new-password` as the new field to prevent automatic
filling.

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

CE upstream - 2018-11-15 18:21 UTC

Closes gitlab-ce#46133

See merge request gitlab-org/gitlab-ee!8475

Enable even more frozen string in lib/gitlab

See merge request gitlab-org/gitlab-ce!22959

https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8475

Display impersonation token value only after creation

See merge request gitlab-org/gitlab-ce!22916

# Conflicts:
#	.gitlab-ci.yml

[ci skip]

Add BUILD_ASSETS_IMAGE CI variable

See merge request gitlab-org/gitlab-ce!23076

Add BUILD_ASSETS_IMAGE CI variable

* Defaults to FALSE
* Can be used to disable building/pushing the assets image in the
gitlab:compile:assets job

See merge request gitlab-org/gitlab-ee!8452

Remove unused project method

Closes #54103

See merge request gitlab-org/gitlab-ce!23124

In a few models we define ActiveRecord enums that are redefined in EE
using the following pattern:

    enum :some_enum, {
      ...
    }.merge(EE_ENUM_VALUES)

This particular approach is problematic to deal with, because it
requires that we `prepend` and EE module _before_ defining the enum.
This typically translates to the `prepend` being the first line in the
model in EE, but this can easily lead to merge conflicts when developers
add more `include` and/or `prepend` lines.

As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8244 and
https://gitlab.com/gitlab-org/gitlab-ee/issues/8241 we are moving
`prepend` to the last line in a file, reducing the chances of running
into merge conflicts. This poses a bit of a problem with the pattern
above, because this pattern does not allow us to move the `prepend`
further down a file.

To resolve this problem, we simply move the Hash value of the enum to a
separate class method. This method is defined in a separate module where
necessary, allowing us to use it like so:

    enum :failure_reasons, ::SomeModelEnums.failure_reasons

The method in turn is defined in a very straightforward manner:

    module SomeModelEnums
      def self.failure_reasons
        {
          ...
        }
      end
    end

This makes it easy for EE to add values without requiring the `prepend`
to be placed before the `enum` is defined.

For more information, see the following issues and merge requests:

* https://gitlab.com/gitlab-org/gitlab-ee/issues/8244
* https://gitlab.com/gitlab-org/gitlab-ee/issues/8241
* https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8424

CE upstream - 2018-11-15 15:21 UTC

Closes gitlab-ce#54059, #8311, and gitaly#1393

See merge request gitlab-org/gitlab-ee!8472

Bump Gitaly version to 0.132.0

See merge request gitlab-org/gitlab-ce!23066

* Defaults to FALSE
* Can be used to disable building/pushing the assets image in the
gitlab:compile:assets job

* Defaults to FALSE
* Can be used to disable building/pushing the assets image in the
gitlab:compile:assets job

Prevents empty button in jobs empty state

Closes #54021

See merge request gitlab-org/gitlab-ce!23072

Remove display of local Sidekiq process in /admin/sidekiq

Closes #46133

See merge request gitlab-org/gitlab-ce!23118

https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8472/

# Conflicts:
#	.gitlab-ci.yml

[ci skip]

Use the new parallel keyword in .gitlab-ci.yml

See merge request gitlab-org/gitlab-ce!23083

[EE] Use the new parallel keyword in .gitlab-ci.yml

See merge request gitlab-org/gitlab-ee!8454

In a cloud-native or high-availability configuration, Sidekiq may not
be running on the same node as the Web worker. The output of the `ps`
output does not work in this case and can mislead admins that
Sidekiq isn't running. Remove it in favor of the Sidekiq dashboard,
which shows local processes using the Redis information.

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