This adds and documents an `alpha_feature_available?` method to groups
and projects, and also documents the existing `beta_feature_available?`
method.

When checking permissions for a group, it always tries to load
group ancestor (to check SSO). If we check permissions for related
groups (for which we are sure that all of them have same root), we
just preset this root group before checking permission.

Previously displayed CI Minutes warning if
last_ci_minutes_usage_notification_level is set on the namespace.

Changed to be displayed if last_ci_minutes_usage_notification_level
is set and shared_runners_minutes_left is still below
last_ci_minutes_usage_notification_level.

* Add unique index
* Add model validation
* Ensure data migration leverages the index

Kamil Trzciński authored Nov 11, 2019 and Heinrich Lee Yu committed Nov 11, 2019

This introduces a persistent `default`
and `free` plans into database.

The `default` is used by all on-premise
installations. The `free` is created for
GitLab.com.

When a trial expires for a namespace, we won't show a new trial
again. This is valid for the user dashboard and user and group billing
pages

It adds an upgrade button to the user billings
page that redirects to the customers portal
upgrade checkout page.

If the user is not logged in at the portal he/she
will be automatically redirected after the login
process.

If the user is at the latest tier, the button
won't be presented and it'll fallback to the
existing plans table.

To protect from accidentally launching too many CI pipelines
we introduce a new JobActivity limit which compare the count
of jobs in alive pipelines created in the past hour.

Ensure that we update namespace statistics together with
project statistics to avoid the two being out of sync.

Extract out scopes into models and remove duplication.

Olivier Gonzalez authored Aug 06, 2019 and James Lopez committed Aug 06, 2019

The corresponding features are running since several releases

This value was deprecated since 11.5 and planned to be dropped for 12.0

Rubén Dávila authored Jul 05, 2019 and James Lopez committed Jul 05, 2019

Mutliple levels of notifications are suppoerted.
We just send the notification when a new level has been reached.

Rubén Dávila authored Jun 12, 2019 and Mayra Cabrera committed Jun 12, 2019

An email is sent to all owners when all CI minutes have been used, this
also includes extra CI minutes.

Removing this feature flag NamespaceStatistcs will be aggregated on
root-namespace matching gitlab.com billing schema

Rubén Dávila authored May 07, 2019 and James Lopez committed May 07, 2019

Changes that were initially added to hide this button has been reverted
given now it's possible to purchase extra CI minutes for free plans.

Add to group spec namespace check

Prepares us for upgrade to Rails 5.2

The ability to purchase extra CI minutes is only available for
Namespaces with a paid plan for now. In order to avoid confusion
we should hide this button when the Namespace is using a Free plan.

* extra_shared_runners_minutes_limit column was added to namespaces.
* extra minutes should roll over to the next month in case customer has
not used all their extra minutes

Mario de la Ossa authored Mar 29, 2019 and Nick Thomas committed Mar 29, 2019

In order to allow us to incrementally enable ES on gitlab.com we add two
 new classes:

- ElasticsearchIndexedNamespaces
- ElasticsearchIndexedProjects

These classes are used by ApplicationSetting to enable/disable projects
and namespaces (groups) that should be indexed by elasticsearch.

We also have the application setting, `elasticsearch_limit_indexing`,
that enables/disables the new functionality

In order to be able to selectively choose projects/namespaces to use
with elasticsearch, `elasticsearch_limit_indexing` MUST be enabled under
the admin integrations options.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Adds helpers to hide the callout if the current
namespace is on a gold plan or trial.
Adds namespace plan matcher methods to Plan.
Adds GoldTrialUserCalloutsHelper to clean up
UserCalloutsHelper.

The GL.com plan is no longer stored with Namespace, now this attribute
is part of the new GitlabSubscription model.

1. ee/app/models/ee/namespace.rb:90
2. ee/app/models/ee/namespace.rb:102
3. ee/app/models/ee/project.rb:520

This is required to avoid an error when re-generating the FK due to
orphaned records. See more https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8871#note_125503270

Enables frozen string in the following:

* ee/app/helpers/**/*.rb
* ee/app/mailers/**/*.rb
* ee/app/models/**/*.rb

Partially addresses gitlab-org/gitlab-ce/#47424.

Extend models to provide necessary logic for security reports.
Add Secuirity Reports ruby classes
Add SAST parser
Add logic to store report in database

When the feature is available, this setting allows admins to choose a
project as a source of custom file templates. This is in addition to
any instance-wide templates, whether custom or vendored into the GitLab
codebase.

We use the flipper gem to provide feature gates in GitLab backed
with the ActiveSupportCacheStore adapter.

In a Geo setup, the primary and secondary do not share Redis state.
This means that changes to a feature on the primary do not invalidate
the cache on the secondary, leading to inconsistent behaviour.

To fix this send a cache invalidation event via the Geo log cursor
whenever features are changed.

The Geo::EventStore#create method doesn't have a ! on the end
of it. It should, since its behaviour is to raise an exception
if the validation or the save fails.