delta/gitlab/gitlab-ce.git/spec/models/project_spec.rb, branch refactor_auto_devops_enabled

Fix typo "beetween" in timeout validation message

2019-07-13T13:29:47+00:00

Remove group_clusters feature flag

2019-06-27T12:28:03+00:00

Now we have terminals for instance and group clusters we can remove the
FF now. Deploying to group clusters has been working without complaints
too.

Remove project-level cluster credential fallback

2019-06-21T03:55:30+00:00

Project-level clusters that made use of this legacy
behaviour have been migrated to unmanaged clusters,
so we are now free to remove this fallback.

Make KubernetesService readonly

2019-06-18T00:01:56+00:00

We are deprecating this service in favor of instance wide clusters.
Therefore we removed some code that is not anymore needed for a
readonly cluster and also we added some flags to allow for this
deprecation. These flags are to be removed in the next release when
we finally completelly remove KubernetesService.

Hashed Storage is enabled by default on new installations

2019-06-17T18:35:22+00:00

updated documentation for Geo

Merge branch '9490-record-repository_type-on-lfs_objects_projects-ce' into 'master'

2019-06-17T13:05:39+00:00

CE backport for gitlab-ee!13894 (Save repository_type to LfsObjectsProject)

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

CE backport for changes in EE MR 13894

2019-06-16T23:23:06+00:00

This backports to CE changes that allow the recording of the
repository_type in the table lfs_objects_projects.

This is in order to allow future pruning of unreferenced LFS objects,
as we will need to know which repository to look in for the LFS pointer
file.

The EE MR that contains the original code and a full explanation of the
changes is
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894

EE Issue https://gitlab.com/gitlab-org/gitlab-ee/issues/9490

Note that there was a lot of CE code changed in the EE MR because we
want to allow the wiki repository to also use LFS. See
https://gitlab.com/gitlab-org/gitlab-ce/issues/43721. As the wiki is
an unlicensed feature, a full backport is required to enable this.

Fix inability to set visibility_level on project via API

2019-06-14T14:36:35+00:00

Consider the scenario:

1. The default visibility level is set to internal
2. A user attempts to create a private project within a private group

Previously this would always fail because default_value_for would
overwrite the private visibility setting, no matter what
visibility_level were specified. This was happening because
default_value_for was confused by the default value of 0 specified by
the database schema.

default_value_for attempts to assign the default value in the block by
checking whether the attribute has changed. The problem is that since
the default value by the database was 0, and the user requested 0, this
appeared as though no changes were made. As a result, default_value_for
would always overwrite the user's preference.

To fix this, we remove the use of default_value_for and only set the
visibility level to the default application setting when no preference
has been given at creation time.

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

Merge dev.gitlab.org master into GitLab.com master

2019-06-03T12:56:33+00:00

Merge branch 'security-fix_milestones_search_api_leak' into 'master'

2019-06-03T12:34:07+00:00

Resolve: Milestones leaked via search API

Closes #2822

See merge request gitlab/gitlabhq!2997