| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Remove ForkedProjectLink model
Closes #38883
See merge request gitlab-org/gitlab-ce!22226
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the `ForkedProjectLink` model that has been replaced by
the `ForkNetworkMember` and `ForkNetwork` combination. All existing
relations have been adjusted to use these new models.
The `forked_project_link` table has been dropped.
The "Forks" count on the admin dashboard has been updated to count all
`ForkNetworkMember` rows and deduct the number of `ForkNetwork`
rows. This is because now the "root-project" of a fork network also
has a `ForkNetworkMember` row. This count could become inaccurate when
the root of a fork network is deleted.
|
|\ \
| | |
| | |
| | |
| | | |
Expose changed URLs in MR ci_environments_status
See merge request gitlab-org/gitlab-ce!22228
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
GET :namespace/merge_requests/:id/ci_environments_status complexity
already reached a limit for a direct serialization from an hash
computed at within the controller function.
Here we introduce a virtual model EnvironmentStatus and its serializer.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Strip whitespace around GitHub personal access tokens
Closes #46588
See merge request gitlab-org/gitlab-ce!22432
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Some browsers insert a trailing whitespace after pasting the
token into the field. This should help reduce confusion.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/46588
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
These headers can be used to build URLs for API requests. Good examples
would be Issues and Merge Requests
|
|/ /
| |
| |
| |
| | |
Before this commit updating Prometheus (e.g. adding alerts) made it
"updated" therefore not installed.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes close/reopen quick actions preview for issues and merge_requests
Closes #52669
See merge request gitlab-org/gitlab-ce!22343
|
| |/
| |
| |
| |
| | |
Close/reopen quick actions preview wasn't shown properly, now the
preview is shown as expected.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
'master'
Fix code reuse issue in Projects::Clusters::ApplicationController#index
See merge request gitlab-org/gitlab-ce!22182
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove the inheritance from ::BaseService which is causing us to inherit
the initializer that has project as the first arg, as we will not have
access to project with forthcoming group clusters.
Also call install service from create service - 1 less thing to re-use
Extract TestRequest code into a spec helper. Given that we need
different behaviour for Rails 5.0 (and again in Rails 5.1!), it's handy
to have that branching behaviour in one place
|
|/ |
|
|
|
|
|
|
|
| |
Was introduced in the time that GitLab still used NFS, which is not
required anymore in most cases. By removing this, the API it calls will
return empty responses. This interface has to be removed in the next
major release, expected to be 12.0.
|
|\
| |
| |
| |
| |
| |
| | |
Preload project features in reference parser
Closes #43094
See merge request gitlab-org/gitlab-ce!22008
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Preloading of project_features mitigates N+1 queries when checking
references in other projects.
When loading projects for resources referenced in comments it
makes sense to include also associated project_features because
in the following step (`can_read_reference?(user, projects[node],
node)`) project features is used for checking permissions for the given
project.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Remove :rbac_clusters feature flag
Closes #51009
See merge request gitlab-org/gitlab-ce!22096
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now that Auto DevOps can run in a RBAC enabled cluster from
https://gitlab.com/gitlab-org/gitlab-ce/issues/51942, we can now remove
the FF.
As the flag only governed if UI elements would appear or not when
creating/adding existing clusters; the effect of removing the FF would
be that the checkbox to choose to enable RBAC clusters will now always
appear.
Remove FF stubs from specs
Improve spec context names
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
Remove Gitlab::Git::Repository#rugged
See merge request gitlab-org/gitlab-ce!22039
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Cleanup code, and refactor tests that still use Rugged. After this, there should
be no Rugged code that access the instance's repositories on non-test
environments. There is still some rugged code for other tasks like the
repository import task, but since it doesn't access any repository storage path
it can stay.
|
|/
|
|
|
|
|
|
|
| |
The pre-release tags are set at the beginning of a release, so it
would be impossible to figure out which version was running if we're
running nightlies.
In that case it's better to still link to the SHA. These versions
don't get deployed to .com.
|
|\
| |
| |
| |
| | |
CE port of Adding state to epics
See merge request gitlab-org/gitlab-ce!21771
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Add fixture path argument to `MarkdownFeature.new`
See merge request gitlab-org/gitlab-ce!21754
|
| |
| |
| |
| |
| | |
This default will be overridden in the EE-specific subclass that uses a
different fixture path.
|
| | |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Support Kubernetes RBAC for GitLab Managed Apps for creating new clusters
Closes #29398
See merge request gitlab-org/gitlab-ce!21401
|
| |
| |
| |
| | |
In our case it's 'default'.
|
| | |
|
| |
| |
| |
| | |
This is similar to the option in the Add Existing cluster form
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
of ABAC/RBAC
This also solves the async nature of the automatic creation of default
service tokens for service accounts. It also makes explicit which
service account token we always use.
create cluster role binding only if the provider has legacy_abac
disabled.
|
| |
| |
| |
| |
| |
| | |
feature flag is enabled
Explicitly persist the legacy_abac value of the cluster_provider_gcp so that we can disable abac if the `:rbac_clusters` feature flag is enabled
|
| |
| |
| |
| |
| |
| |
| | |
GitLab can perform operations in a RBAC-enabled cluster.
Correspondingly, use the token of the gitlab service account, vs the
default service account token which will have no privs.
|
|\ \
| |/
|/|
| |
| | |
CE: Properly implement prepending for Concern
See merge request gitlab-org/gitlab-ce!21444
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Remove Rugged and shell code from Gitlab::Git
Closes gitaly#1124
See merge request gitlab-org/gitlab-ce!21488
|
| |/ |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Add /lock and /unlock quick actions
Closes #39173
See merge request gitlab-org/gitlab-ce!15197
|
| |
| |
| |
| |
| |
| | |
Devise helpers acts on Warden which is faster than our own helpers.
Note that `gitlab_sign_out` is still necessary due to the same issue
mentioned at 60814985e033e4941ff3eb5d33ca55e3fc81593e
|
| | |
|
| |
| |
| |
| | |
Leftover from ea090291.
|
| |
| |
| |
| | |
Closes #39173
|
|\ \
| | |
| | |
| | |
| | | |
Disable query limit counter in sidekiq
See merge request gitlab-org/gitlab-ce!21470
|
| | |
| | |
| | |
| | |
| | | |
Inside Sidekiq the request is whitelisted to
avoid increasing query counter.
|
| | |
| | |
| | |
| | |
| | | |
This is similar to https://gitlab.com/gitlab-org/gitlab-ee/issues/7511, but
the root cause is https://gitlab.com/gitlab-org/gitlab-ce/issues/51268.
|
| | |
| | |
| | |
| | |
| | | |
Labels are sorted by reference, not title. This caused random CI
failure.
|