| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Set the name of a user-namespace to the user name
See merge request gitlab-org/gitlab-ce!23272
|
|
Updates changed method names and fixes spec failures
|
|
Add CI variable to provide GitLab FQDN
Closes #64161
See merge request gitlab-org/gitlab-ce!30417
|
|
Make sure all specs run properly
See merge request gitlab-org/gitlab-ce!30367
|
|
- handling properties needs to be skipped when
creating test records in order to test the legacy
data
|
|
Banzai - avoid redis if attr is in DB cache
See merge request gitlab-org/gitlab-ce!30334
|
|
When cache_collection_render runs we end up reading and writing
things to redis even if we already have the rendered field cached
in the DB. This commit avoids using redis at all whenever we have
the field already rendered in the DB cache.
|
|
This brings the rspec-core version in line with the Gitaly changes
and introduces Rails 5.1/5.2 improvements.
Full CHANGELOG:
https://github.com/rspec/rspec-rails/blob/master/Changelog.md
|
|
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|
|
Prepare cycle analytics for group level
See merge request gitlab-org/gitlab-ce!30356
|
|
Fix rubocop offences
|
|
A new `discussion_id` argument on the `createNote` mutation allows
people to create a note within that discussion.
The ability to lazy-load Discussions has been added, so
GraphQL.object_from_id can treat Discussions the same as AR objects and
batch load them.
https://gitlab.com/gitlab-org/gitlab-ce/issues/62826
https://gitlab.com/gitlab-org/gitlab-ee/issues/9489
|
|
|
|
Instead of setting the name of the namespace to the user's username,
set it to the user's name.
This is more consistent with how we name the routes:
The route-name of a namespace is the human name of the routable. In
the case of a user-namespace, this is the owner's name.
When we change a user's name (both on create and update), we now also
update the namespace-name to the user's name. This will make sure that
if we also correctly update all the nested routes.
|
|
|
|
|
|
|
|
|
|
Allow ReactiveCaching to support nil value
See merge request gitlab-org/gitlab-ce!30456
|
|
Schedules a Namespace::AggregationSchedule worker if some of the project
statistics are refreshed.
The worker is only executed if the feature flag is enabled.
|
|
When :calculate_reactive_caching returns a nil value
this caused ReactiveCaching to schedule a worker
every time the code using :with_reactive_cache was called.
This issue caused an increasing amount of Sidekiq jobs
being created continuously.
Implementing this fix behind feature flag
:reactive_caching_check_key_exists
|
|
CE Port: Fix race condition of `refs/merge` competing overwrite
See merge request gitlab-org/gitlab-ce!30308
|
|
Reduce N+1 queries in MergeRequestsController#ci_environment_status
See merge request gitlab-org/gitlab-ce!30224
|
|
Remove minimum required characters for fuzzy search if no trigram is used
See merge request gitlab-org/gitlab-ce!29810
|
|
Today, Pipelines for merge train run on `refs/merge`,
however, this causes a race condition that it can be
overwritten by CheckMergeabilityService.
This patch fixes the problem by generating `refs/train`
for those pipelines.
|
|
- This enables us to use a scope to query all clusters in group
hierarchy order in one query, and also enables us to union to instance
clusters later.
- Handle case where clusters not present at level. In which case the
query should go ahead and return the next level's clusters.
- Swap with new CTE query behind Feature flag. This FF is default
disabled.
|
|
In 12.2 we will remove this fallback.
|
|
We stopped calling the fallback so we can remove this now
|
|
We can now share project so that we don't have to load project twice.
Also, this extracts non-relevant logic out of Deployment.
Update DeploymentsController accordingly
|
|
Otherwise, each EnvironmentStatus object instantiates its own project
when really they are the same. Improves query count performance
|
|
This improves query performance of
MergeRequestsController#ci_environments_status a lot.
However this means old deployments that deployed to kubernetes clusters
with prometheus installations will no longer show performance metrics as
we cannot backfill cluster_id from deployment_platform with certainty
(clusters may be edited/added/deleted, which changes the results of
deployment_platform).
|
|
When `ReactiveCachingWorker` hits an SSL or other exception that occurs
quickly and reliably, automatically rescheduling a new worker could lead
to excessive number of jobs being scheduled. This happens because not
only does the failed job get rescheduled in a minute, but each Sidekiq
retry will also add even more rescheduled jobs.
In busy instances, this can become an issue because large numbers of
`ReactiveCachingWorker` running can cause high rates of `ExclusiveLease`
reads to occur and possibly saturate the Redis server with queries.
We now disable this automatic retry and rely on Sidekiq to perform its 3
retries with a backoff period.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64176
|
|
Some services can raise OpenSSL::X509::CertificateError due
to an invalid SSL certificates, with OpenSSL::OpenSSLError
we can handle these errors.
|
|
CE Port: Extend `MergeToRefService` to create merge ref from an arbitrary ref
See merge request gitlab-org/gitlab-ce!30361
|
|
Currently, MergeToRefService is specifically designed for
createing merge commits from source branch and target branch of
merge reqeusts. We extend this behavior to source branch and any
target ref paths.
|
|
Now that KubernetesService can no longer be a DeploymentPlatform we can
remove all kubernetes client code and KubernetesService edge cases.
|
|
If we're not using a trigram index, then ignore the
min_chars_for_partial_matching setting
|
|
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
|
Sets lease_release? to false to prevent the job to be re-executed more
often than lease timeout
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64079
|
|
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|
Use the shared method in Ci::Pipeline
|
|
When file_mover_spec.rb ran, it would initialize fog-aws with
`Fog::AWS::Storage::Real` service instead of `Fog::AWS::Storage::Mock`
because `Fog.mock!` was not called. Ensure that we use
`stub_uploads_object_storage` to prevent that from happening.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64083
|
|
|
|
The auto_devops object sometimes doesn't exists. We may need to create
it.
|
|
We map the boolean to the string 'fetch' or 'clone', to be more
explicit.
|
|
- issues_access_level
- repository_access_level
- merge_requests_access_level
- builds_access_level
- wiki_access_level
- snippets_access_level
|
|
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
|
This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.
Empty usernames will be saved as null in the database.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.
|
