| Age | Commit message (Collapse) | Author |
|---|
|
Commit messages are not processed for references to issues when
creating the default branch on push. This was expected
behavior (probably to avoid performance problems when first pushing a
repository with thousands of commits). However, this is not an issue
because we always limit the number of commits to process to 100
regardless of whether we are creating the default branch or not.
|
|
AddToMergeTrainWhenPipelineSucceeds and MergeTrain
|
|
Expose default_git_depth via project API
Closes #62908
See merge request gitlab-org/gitlab-ce!29353
|
|
Enable Get and Update of ci_default_git_depth for
Project API.
Renaming Project#default_git_depth to :ci_default_git_depth
to give more context through the API usage.
Add API documentation
|
|
Currently, merge options is updated on #execute method,
however, we should have #update interface to make it explicit.
|
|
|
|
Fix pipeline schedule when owner is nil
Closes gitlab-com/gl-infra/production#805 and #63086
See merge request gitlab-org/gitlab-ce!29477
|
|
Fixing the bug
|
|
Notify events when auto merge is enabled or merge param is updated
See merge request gitlab-org/gitlab-ce!29415
|
|
When target branch is updated, Auto Merge should be canceled.
|
|
There are bunch of auto merge related notifications, and
when auto merge is enabled, it should be evaluated immediately.
|
|
'master'
Remove extraneous DiffNote#supports_suggestion? calls
See merge request gitlab-org/gitlab-ce!29027
|
|
Add project level git depth setting
Closes #59688
See merge request gitlab-org/gitlab-ce!28919
|
|
Extract acme double to helper
Create ACME challanges for pages domains
* Create order & challange through API
* save them to database
* request challenge validation
We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain
Add controller for processing acme challenges redirected from pages
Don't save acme challenge url - we don't use it
Validate acme challenge attributes
Encrypt private_key in acme orders
|
|
Create BaseService for Auto Merge architecture
See merge request gitlab-org/gitlab-ce!29120
|
|
If the origin project has no default_git_depth set (i.e. nil) set the
fork's default_git_depth to 0
|
|
Introduce default_git_depth in project's CI/CD settings and set it to
50. Use it if there is no GIT_DEPTH variable specified. Apply this
default only to newly created projects and keep it nil for old ones
in order to not break pipelines that rely on non-shallow clones.
default_git_depth can be updated from CI/CD Settings in the UI, must be
either nil or integer between 0 and 1000 (incl).
Inherit default_git_depth from the origin project when forking projects.
MR pipelines are run on a MR ref (refs/merge-requests/:iid/merge) and it
contains unique commit (i.e. merge commit) which doesn't exist in the
other branch/tags refs. We need to add it cause otherwise it may break
pipelines for old projects that have already enabled Pipelines for merge
results and have git depth 0.
Document new default_git_depth project CI/CD setting
|
|
It abstracts some codes for common methods in AutoMerge::*Services.
|
|
We don't have a way to create MR pipeline today, this is one
of the headaches for users.
This change is a preliminary work for the capability.
|
|
|
|
It looks to be a stub/mock rather than strictly an expectation of the
system, so dropping this to only a single invocation expected, as we've
removed one of the two places #last_diff_file would be invoked.
|
|
Delete Todos for guest users when project visibility
level is updated to private.
|
|
Cancel auto merge when merge request is closed
See merge request gitlab-org/gitlab-ce!28782
|
|
'set-real-next-run-at-for-preventing-duplciate-pipeline-creations' into 'master'
Make pipeline schedule worker resilient
Closes gitlab-com/gl-infra/production#805 and #61955
See merge request gitlab-org/gitlab-ce!28407
|
|
We should cancel auto merge when merge request is closed.
|
|
Automatically update MR merge-ref along merge status
Closes #58495
See merge request gitlab-org/gitlab-ce!28513
|
|
|
|
Disallow invalid MR branch name
See merge request gitlab/gitlabhq!3052
|
|
We have one auto merge strategy today - Merge When Pipeline
Succeeds.
In order to add more strategies for Merge Train feature,
we abstract the architecture to be more extensible.
Removed arguments
Fix spec
|
|
Currently, pipeline schedule worker is unstable because it's
sometimes killed by excessive memory consumption.
In order to improve the performance, we add the following fixes:
1. next_run_at is always real_next_run, which means the value
always takes into account of worker's cron schedule
1. Remove exlusive lock. This is already covered by real_next_run
change.
1. Use RunPipelineScheduleWorker for avoiding memory killer.
Memory consumption is spread to the multiple sidekiq worker.
|
|
This introduces payload to the ServiceResponse with
the merge ref HEAD commit data
|
|
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.
|
|
We've already migrated all the legacy artifacts to the new realm,
which is ci_job_artifacts table.
It's time to remove the old code base that is no longer used.
|
|
Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
blocked, and then uses the same IP to perform the actual request, while
passing the original hostname in the `Host` header and SSL SNI field.
|
|
|
|
Before this fix, a suggestion which just removes
an empty line wasn't appliable
|
|
57825-moving-an-issue-results-in-broken-image-links-in-comments
|
|
|
|
|
|
|
|
'61935-remove-code-left-over-from-when-clusters-were-always-project-specific' into 'master'
remove `Clusters::Platforms::Kubernetes#actual_namespace`
Closes #61935
See merge request gitlab-org/gitlab-ce!28391
|
|
Add GitDeduplicationService
Closes #60871
See merge request gitlab-org/gitlab-ce!28144
|
|
Move some project routes under /-/ scope
See merge request gitlab-org/gitlab-ce!28435
|
|
GitDeduplicationService performs idempotent operations on deduplicated
projects.
|
|
When Kubernetes clusters were originally built they could only
exist at the project level, and so there was logic included
that assumed there would only ever be a single Kubernetes
namespace per cluster. We now support clusters at the group
and instance level, which allows multiple namespaces.
This change consolidates various project-specific fallbacks to
generate namespaces, and hands all responsibility to the
Clusters::KubernetesNamespace model. There is now no concept of
a single namespace for a Clusters::Platforms::Kubernetes; to
retrieve a namespace a project must now be supplied in all cases.
This simplifies upcoming work to use a separate Kubernetes
namespace per project environment (instead of a namespace
per project).
|
|
|
|
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|
Fix remote mirrors not updating after tag push
Closes #51240
See merge request gitlab-org/gitlab-ce!28430
|
|
Remote mirrors were only being updated after pushes to branches, not
tags. This change consolidates the functionality into
Git::BaseHooksService so that both tags and branches will now update
remote mirrors.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/51240
|
|
Immediate configuration is not ideal for group and instance
level clusters as projects that may never be deployed would
still have Kubernetes namespaces and service accounts created
for them.
As of https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25586
we now create only the resources that are required for the
project being deployed, at the time of deployment.
|
