| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
When this option is enabled, GitLab will create namespaces and service
accounts as usual. When disabled, GitLab wont create any project
specific kubernetes resources
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56557
|
| |
|
|
|
|
|
|
| |
PackRefs is not an expensive gitaly call - we want to
call it more often (than as part of full `gc`) because
it helps to keep number of refs files small - too many
refs file may be a problem for deployments with
slow storage.
|
| |
|
|
|
| |
Domain will be removed by verification worker after 1 week
of being disabled
|
| |
|
|
| |
+ to monitor progress of uninstallation pod
|
| |\
| |
| |
| |
| |
| |
| | |
Prevent concurrent execution of PipelineScheduleWorker
Closes gitlab-com/gl-infra/production#805
See merge request gitlab-org/gitlab-ce!27781
|
| | |
| |
| |
| |
| |
| | |
Currently, PipelineScheduleWorker is fired in a short period on
our production server. We can stop this behavior by locking the
execution thread with in_lock method.
|
| |/
|
|
|
| |
This enables sending a chat message to Slack or Mattermost
upon a successful, failed, or canceled deployment
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
'60500-disable-jit-kubernetes-resource-creation-for-project-level-clusters' into 'master'
Disable JIT Kubernetes resource creation for project level clusters
Closes #60500
See merge request gitlab-org/gitlab-ce!27352
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
JIT resource creation blocks deployments if a user is
self-managing their cluster, as it will fail the build
if unable to create a namespace and service account.
Using a custom namespace and service account was previously
supported for project level clusters, so we should preserve
this functionality.
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27352
|
| |/
|
|
|
|
|
|
|
|
|
| |
When deleting a pipeline, only some of the cache structures were being
expired, but not the full pipeline list. We have to synchronously
schedule a pipeline cache expiration because the pipeline will be
deleted if the Sidekiq expiration job picks it up. To do this, properly
extract all the logic buried in the Sidekiq worker into a service, and
then call the service.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60469
|
| |
|
|
|
|
|
|
| |
This adds a limitation that we will try to create pipeline
for at most 4 first changes (branches and tags).
This does not affect processing of Pipelines for Merge Requests,
as each updated MR will have associated pipeline created.
|
| |\
| |
| |
| |
| | |
Fix the bug that the project statistics is not updated
See merge request gitlab-org/gitlab-ce!26854
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
| |
Adds `# frozen_string_literal: true` to spec/workers ruby files
|
| |
|
|
|
|
|
|
|
|
| |
Since external diffs are likely to be a bit slower than in-database
ones, add a mode that makes diffs external after they've been obsoleted
by events. This should strike a balance between performance and disk
space.
A background cron drives the majority of migrations, since diffs become
outdated through user actions.
|
| | |
|
| | |
|
| |
|
|
|
| |
The flag is on by default, but allows us to revert back
to the old behaviour if we encounter any problems.
|
| |
|
|
|
|
|
|
|
| |
Introduces the concept of Prerequisites for a CI build.
If a build has unmet prerequisites it will go through the
:preparing state before being made available to a runner.
There are no actual prerequisites yet, so current
behaviour is unchanged.
|
| |\ |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Hashed Storage rollback mechanism
See merge request gitlab-org/gitlab-ce!23955
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Rollback is done similar to Migration for the Hashed Storage.
It also shares the same ExclusiveLease key to prevent both happening
at the same time.
All Hashed Storage related workers now share the same queue namespace
which allows for assigning dedicated workers easily.
|
| | | |
| | |
| | |
| | |
| | | |
Moved to HashedStorage namespace, and added them to the
`:hashed_storage` queue namespace
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
We are adding sidekiq workers and service classes to allow to rollback
a hashed storage migration. There are some refactoring involved as well
as part of the code can be reused by both the migration and the rollback
logic.
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix
ok
Add spec
Fix
ok
Fix
Add changelog
Fix
Add memoization
a
fix
|
| |/
|
|
|
|
| |
The API get projects/:id/traffic/fetches allows user with write
access to the repository to get the number of clones for the
last 30 days.
|
| |
|
|
| |
ChatOps used to be in the Ultimate tier.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is what was happening before:
1. `Project#set_timestamps_for_create` was called at creation time
and set the `last_activity_at` and `last_repository_updated_at`
to the current timestamp T.
2. The test ran `PostReceive#perform`, which then called
`PostReceive#process_wiki_changes`. If less than 500 milliseconds
elapsed since T, then the update would just set the timestamp to T.
To fix this problem, we can just use Timecop to ensure at least
one second has elapsed after attempting to process changes.
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/8871
|
| |
|
|
| |
Use project models instead of a list of parameters.
|
| |
|
|
|
|
|
| |
When hashed storage is in use, it's helpful to have the project
name associated with the request.
Closes https://gitlab.com/gitlab-org/gitaly/issues/1394
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Specs were reviewed and improved to better cover the current behavior.
There was some standardization done as well to facilitate the
implementation of the rollback functionality.
StorageMigratorWorker was extracted to HashedStorage namespace were
RollbackerWorker will live one as well.
|
| |
|
|
|
| |
This is part of the refactor to include a RollbackService into
HashedStorage module
|
| |
|
|
| |
We are keeping compatibility with existing scheduled jobs.
|
| |\
| |
| |
| |
| |
| |
| | |
Container repository cleanup API
Closes #55978
See merge request gitlab-org/gitlab-ce!24303
|
| | |
| |
| |
| |
| |
| | |
This includes a set of APIs to manipulate container registry.
This includes also an ability to delete tags based on requested
criteria, like keep-last-n, matching-name, older-than.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Enable the Layout/ExtraSpacing cop
Closes #56392
See merge request gitlab-org/gitlab-ce!24423
|
| | |/
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename
Introduce Destroy expired job artifacts service
Revert a bit
Add changelog
Use expired
Improve
Fix spec
Fix spec
Use bang for destroy
Introduce iteration limit
Update comment
Simplify more
Refacor
Remove unnecessary thing
Fix comments
Fix coding offence
Make loop helper exception free
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Retries in Sidekiq and in the remote mirror scheduler can cause repeated
attempts in quick succession if the sync fails. Each failure will then
send an e-mail to all project maintainers, which can spam users
unnecessarily.
Modify the logic to send one notification the first time the mirror
fails by setting `error_notification_sent` to `true` and reset the
flag after a successful sync.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56222
|
| |
|
|
|
|
|
|
|
| |
In theory the case could happen that the initial linking of the pool
fails and so do all the retries that Sidekiq performs. This could lead
to data loss.
To prevent that case, linking is done before Gits GC too. This makes
sure that case doesn't happen.
|
| |\
| |
| |
| |
| |
| |
| | |
Import issues from CSV
Closes #49231
See merge request gitlab-org/gitlab-ce!23532
|
| | |
| |
| |
| | |
Process CSV uploads async using a worker then email results
|
| |/
|
|
| |
Sort out some logic
|
| |\
| |
| |
| |
| | |
Bump Ruby on Rails to 5.0.7.1
See merge request gitlab-org/gitlab-ce!23396
|
