Commit 36beda8b authored by James Lopez's avatar James Lopez

Merge branch 'ce-to-ee-2018-07-11' into 'master'

CE upstream - 2018-07-11 12:23 UTC

See merge request gitlab-org/gitlab-ee!6462
parents 3ee4d98e 18dfc289
...@@ -259,6 +259,24 @@ verification requirement. Navigate to `Admin area ➔ Settings` and uncheck ...@@ -259,6 +259,24 @@ verification requirement. Navigate to `Admin area ➔ Settings` and uncheck
**Require users to prove ownership of custom domains** in the Pages section. **Require users to prove ownership of custom domains** in the Pages section.
This setting is enabled by default. This setting is enabled by default.
## Activate verbose logging for daemon
Verbose logging was [introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2533) in
Omnibus GitLab 11.1.
Follow the steps below to configure verbose logging of GitLab Pages daemon.
1. By default the daemon only logs with `INFO` level.
If you wish to make it log events with level `DEBUG` you must configure this in
`/etc/gitlab/gitlab.rb`:
```shell
gitlab_pages['log_verbose'] = true
```
1. [Reconfigure GitLab][reconfigure]
## Change storage path ## Change storage path
Follow the steps below to change the default path where GitLab Pages' contents Follow the steps below to change the default path where GitLab Pages' contents
......
...@@ -96,8 +96,9 @@ To add an existing Kubernetes cluster to your project: ...@@ -96,8 +96,9 @@ To add an existing Kubernetes cluster to your project:
you can follow the you can follow the
[Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/) [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/)
to create one. You can also view or create service tokens in the to create one. You can also view or create service tokens in the
[Kubernetes dashboard](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/#config) [Kubernetes dashboard](https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/)
(under **Config > Secrets**). (under **Config > Secrets**). **The account that will issue the service token
must have admin privileges on the cluster.**
- **Project namespace** (optional) - You don't have to fill it in; by leaving - **Project namespace** (optional) - You don't have to fill it in; by leaving
it blank, GitLab will create one for you. Also: it blank, GitLab will create one for you. Also:
- Each project should have a unique namespace. - Each project should have a unique namespace.
......
...@@ -138,15 +138,23 @@ module Gitlab ...@@ -138,15 +138,23 @@ module Gitlab
def ee_branch_presence_check! def ee_branch_presence_check!
ee_remotes.keys.each do |remote| ee_remotes.keys.each do |remote|
[ce_branch, ee_branch_prefix, ee_branch_suffix].each do |branch| output, _ = step(
_, status = step("Fetching #{remote}/#{branch}", %W[git fetch #{remote} #{branch}]) "Searching #{remote}",
%W[git ls-remote #{remote} *#{minimal_ee_branch_name}*])
if status.zero? branches =
@ee_remote_with_branch = remote output.scan(%r{(?<=refs/heads/|refs/tags/).+}).sort_by(&:size)
@ee_branch_found = branch
return true next if branches.empty?
end
end branch = branches.first
step("Fetching #{remote}/#{branch}", %W[git fetch #{remote} #{branch}])
@ee_remote_with_branch = remote
@ee_branch_found = branch
return true
end end
puts puts
...@@ -271,6 +279,10 @@ module Gitlab ...@@ -271,6 +279,10 @@ module Gitlab
@ee_patch_full_path ||= patches_dir.join(ee_patch_name) @ee_patch_full_path ||= patches_dir.join(ee_patch_name)
end end
def minimal_ee_branch_name
@minimal_ee_branch_name ||= ce_branch.sub(/(\Ace\-|\-ce\z)/, '')
end
def patch_name_from_branch(branch_name) def patch_name_from_branch(branch_name)
branch_name.parameterize << '.patch' branch_name.parameterize << '.patch'
end end
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment