delta/gitlab/gitlab-ce.git/db, branch fix-diff-system-note-alignment

Avoid DB timeouts when scheduling migrations

2019-06-10T16:35:11+00:00

Revert "Merge branch '50070-legacy-attachments' into 'master'"

2019-06-09T12:56:11+00:00

This reverts commit fd19f887dfeeeedb483c4a4fb32f9f768e89389c, reversing
changes made to abb2d4c601d796339c8d7cb0c00946696730f198.

Merge branch '62418-project-default-git-depth' into 'master'

2019-06-07T10:01:52+00:00

Add project level git depth setting

Closes #59688

See merge request gitlab-org/gitlab-ce!28919

Merge branch '50070-legacy-attachments' into 'master'

2019-06-07T09:50:46+00:00

Migrate legacy uploads

Closes #57217

See merge request gitlab-org/gitlab-ce!24679

Add certificate valid time to pages domain table

2019-06-06T19:14:09+00:00

Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration

Add pages domains acme orders

2019-06-06T18:55:31+00:00

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

Revert "Merge branch 'pages-domain_ssl-valid-period' into 'master'"

2019-06-06T13:57:50+00:00

This reverts merge request !28743

Migrate legacy uploads to the project location

2019-06-06T13:33:04+00:00

Uploads coming from AttachmentUploader
need to be moved to the currently supported location
(FileUploader)

Add certificate valid time to pages domain table

2019-06-06T13:20:15+00:00

Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration

Add project level git depth setting

2019-06-06T08:21:18+00:00

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