| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Since this scope is used in both the controller and the API, we rename
it to make it clear that it's used for both.
|
| |\
| |
| |
| |
| |
| |
| | |
Fix label serialisation in issue and note hooks
Closes #63473
See merge request gitlab-org/gitlab-ce!29850
|
| | |
| |
| |
| |
| | |
Based on review comment fetching labels hook_attrs is now
wrapped in an issue's model method.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
FIX: Scheduled pipelines scheduled to run at the same time as pipeline_schedule_worker gets pushed to the next run
Closes #63469
See merge request gitlab-org/gitlab-ce!29848
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If pipeline schedule is to run at the exact same time with when cron
worker runs, the pipeline schedule will not be executed at the
ideal timing.
We fix this bug by comparing the exact matching of ideal and
cron worker's next run at.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Automatically update MR merge-ref along merge status
See merge request gitlab-org/gitlab-ce!29569
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This couples the code that transitions the `MergeRequest#merge_status`
and refs/merge-requests/:iid/merge ref update.
In general, instead of directly telling `MergeToRefService` to update
the merge ref, we should rely on `MergeabilityCheckService` to keep
both the merge status and merge ref synced. Now, if the merge_status is
`can_be_merged` it means the merge-ref is also updated to the latest.
We've also updated the logic to be more systematic and less user-based.
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'17690-Protect-TeamCity-builds-for-triggering-when-a-branch-is-deleted-And-add-MR-option' into 'master'
Skip TeamCity trigger on branch delete and support MR triggers
Closes #13871 and #17690
See merge request gitlab-org/gitlab-ce!29836
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
DroneCI and TeamCity shared the same validations methods
on the data received. These validations were extracted
into a concern
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a take over from a community contribution:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20990
Skip TeamCity push event when related to branch delete
Support merge request events for TeamCity service.
Add checkbox for merge request triggers in the TeamCity
configuration page.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Enable JIT Kubernetes resource creation for project level clusters
See merge request gitlab-org/gitlab-ce!29515
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously this behaviour was only available to group
and instance-level clusters, as some project clusters
relied on Kubernetes credentials being passed through
to the runner instead of having their resources managed
by GitLab (which is not available when using JIT). These
clusters have been migrated to unmanaged, so resources
can be created on demand for the remaining managed clusters.
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Re-add ignore_column for import columns
See merge request gitlab-org/gitlab-ce!29959
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
This `ignore_column` was present for a while but recently removed, but
to ensure we don't get error 500s let's keep it for a while.
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Improve #has_metrics? and Environment#has_terminals?
See merge request gitlab-org/gitlab-ce!29847
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Success is relatively cheap compared to prometheus_adapter which can
invoke deployment_platform which does a lot of work
|
| | | | | |
| | | | |
| | | | |
| | | | | |
available? is much cheaper than deployment_platform
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
If environment is not available, then no point running the more
expensive `prometheus_adapter`.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds enum certificate_source to pages_domains table
with default manually_uploaded
Mark certificates as 'gitlab_provided'
if the were obtained through Let's Encrypt
Mark certificates as 'user_provided' if they were uploaded through
controller or api
Only show private key in domain edit form if it is 'user_provided'
Only show LetsEncrypt option if is enabled by application settings
(and feature flag)
Refactor and fix some specs to match new logic
Don't show Let's Encrypt certificates as well
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Do not rewrite relative links for system notes
Closes #63162
See merge request gitlab-org/gitlab-ce!29825
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Remove Kubernetes service from deployment platform
See merge request gitlab-org/gitlab-ce!29786
|
| | | | | | |
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | | |
This will no longer be used for deployments, as all
service templates have been migrated to clusters.
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21497, we
migrated all project import data into a separate table,
`project_import_data`. In addition, we also added:
```
ignore_column :import_status, :import_jid, :import_error
```
In https://gitlab.com/gitlab-com/gl-infra/production/issues/908, we
observed some of these `import_error` columns consumed megabytes of
error backtraces and caused slow loading of projects whenever a `SELECT
* from projects` query loaded the row into memory.
Since we have long migrated away from these columns, we can now drop
these columns entirely.
|
| |/ / |
|
| |/
|
|
|
| |
Disabled password authentication for the users registered using
omniauth-ultraauth strategy
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
'60617-allow-switching-from-gitlab-managed-to-unmanaged-clusters' into 'master'
Allow switching clusters between managed/unmanaged
Closes #60617
See merge request gitlab-org/gitlab-ce!29322
|
| | |
| |
| |
| |
| |
| | |
Any resources created while the cluster was managed
will be untouched, allowing users to set/unset this
flag as they please.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |\ \
| |/
|/|
| |
| | |
Migrate Kubernetes service integration templates to clusters
See merge request gitlab-org/gitlab-ce!28534
|
| | |
| |
| |
| |
| | |
Since they are not GitLab managed we wont make assumptions about the
namespaces used
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Don't use Kubernetes namespaces with no token
See merge request gitlab-org/gitlab-ce!29643
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Whenever we are selecting a namespace to use for a
deployment or to query a cluster we want to exclude
Kubernetes namespace records that don't have a token
set as they will not have the required permissions.
However when configuring clusters, we want to
use the original namespace record even if it has no
token, as a namespace has to be unique on a cluster.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Expose currently supported events properly on services API
Closes #56737
See merge request gitlab-org/gitlab-ce!29736
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Create models for issue trackers data
See merge request gitlab-org/gitlab-ce!28598
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- create tables for storing issue trackers properties
- add model and basic logic & spec
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
'master'
CE backport for gitlab-ee!13894 (Save repository_type to LfsObjectsProject)
See merge request gitlab-org/gitlab-ce!29179
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
Closes #63158
See merge request gitlab-org/gitlab-ce!29578
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Expose comments on Noteables in GraphQL
Closes #62825
See merge request gitlab-org/gitlab-ce!29212
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This exposes `Note`s on Issues & MergeRequests using a
`Types::Notes::NoteableType` in GraphQL.
Exposing notes on a new type can be done by implementing the
`NoteableType` interface on the type. The presented object should
be a `Noteable`.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56523
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | | |
inherit require 2fa for all subgroups and projects
See merge request gitlab-org/gitlab-ce!24965
|
| | | | | | | |
|
