Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2020-07-13 00:09:24 +00:00
parent 5236c06e73
commit 1817a9cb6d
42 changed files with 94 additions and 46 deletions

View File

@ -448,7 +448,7 @@ On your GitLab project repository navigate to the **Registry** tab.
![container registry page empty image](img/container_registry_page_empty_image.png)
You may need to [enable Container Registry](../../../user/packages/container_registry/index.md#enable-the-container-registry-for-your-project) to your project to see this tab. You'll find it under your project's **Settings > General > Permissions**.
You may need to [enable Container Registry](../../../user/packages/container_registry/index.md#enable-the-container-registry-for-your-project) to your project to see this tab. You'll find it under your project's **Settings > General > Visibility, project features, permissions**.
To start using Container Registry on our machine, we first need to login to the GitLab registry using our GitLab username and password:

View File

@ -102,7 +102,7 @@ The fair usage algorithm assigns jobs in this order:
1. Job 6 is next, because Project 3 is the only project left with no running jobs.
1. Lastly we choose Job 3... because, again, it's the only job left.
#### Enable a shared Runner
#### Enable shared Runners
On GitLab.com, [shared Runners](#shared-runners) are enabled in all projects by
default.
@ -110,12 +110,31 @@ default.
On self-managed instances of GitLab, an administrator must [install](https://docs.gitlab.com/runner/install/index.html)
and [register](https://docs.gitlab.com/runner/register/index.html) them.
You can also enable or disable shared Runners for individual projects.
You can also enable shared Runners for individual projects.
To enable or disable a shared Runner:
To enable shared Runners:
1. Go to the project's **{settings}** **Settings > CI/CD** and expand the **Runners** section.
1. Click **Allow shared Runners** or **Disable shared Runners**.
1. Click **Allow shared Runners**.
#### Disable shared Runners
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/23123) for groups in GitLab 13.2.
You can disable shared Runners for individual projects or for groups.
You must have Owner permissions for the project or group.
To disable shared Runners for a project:
1. Go to the project's **{settings}** **Settings > CI/CD** and expand the **Runners** section.
1. In the **Shared Runners** area, click **Disable shared Runners**.
To disable shared Runners for a group:
1. Go to the group's **{settings}** **Settings > CI/CD** and expand the **Runners** section.
1. In the **Shared Runners** area, click **Disable shared Runners globally**.
1. Optionally, to allow shared Runners to be enabled for individual projects or subgroups,
click **Allow projects/subgroups to override the global setting**.
### Group Runners
@ -137,14 +156,43 @@ To create a group Runner:
1. Note the URL and token.
1. [Register the Runner](https://docs.gitlab.com/runner/register/).
#### View and manage group Runners
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/37366/) in GitLab 13.2.
You can view and manage all Runners for a group, its subgroups, and projects.
You can do this for your self-managed GitLab instance or for GitLab.com.
You must have [Owner permissions](../../user/permissions.md#group-members-permissions) for the group.
1. Go to the group where you want to view the Runners.
1. Go to **{settings}** **Settings > CI/CD** and expand the **Runners** section.
1. The following fields are displayed.
| Attribute | Description |
| ------------ | ----------- |
| Type | One or more of the following states: shared, group, specific, locked, or paused |
| Runner token | Token used to identify the Runner, and which the Runner uses to communicate with the GitLab instance |
| Description | Description given to the Runner when it was created |
| Version | GitLab Runner version |
| IP address | IP address of the host on which the Runner is registered |
| Projects | The count of projects to which the Runner is assigned |
| Jobs | Total of jobs run by the Runner |
| Tags | Tags associated with the Runner |
| Last contact | Timestamp indicating when the GitLab instance last contacted the Runner |
From this page, you can edit, pause, and remove Runners from the group, its subgroups, and projects.
#### Pause or remove a group Runner
You can pause or remove a group Runner.
You can pause or remove a group Runner for your self-managed GitLab instance or for GitLab.com.
You must have [Owner permissions](../../user/permissions.md#group-members-permissions) for the group.
1. Go to the group you want to remove or pause the Runner for.
1. Go to **{settings}** **Settings > CI/CD** and expand the **Runners** section.
1. Click **Pause** or **Remove Runner**.
- If you pause a group Runner that is used by multiple projects, the Runner pauses for all projects.
- From the group view, you cannot remove a Runner that is assigned to more than one project.
You must remove it from each project first.
1. On the confirmation dialog, click **OK**.
### Specific Runners

View File

@ -19,7 +19,7 @@ This option is available only if your GitLab administrator has
After the Composer Repository is enabled, it will be available for all new projects
by default. To enable it for existing projects, or if you want to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -22,7 +22,7 @@ This option is available only if your GitLab administrator has
After the Conan Repository is enabled, it will be available for all new projects
by default. To enable it for existing projects, or if you want to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -23,7 +23,7 @@ After the Packages feature is enabled, the Maven Repository will be available fo
all new projects by default. To enable it for existing projects, or if you want
to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -25,7 +25,7 @@ This option is available only if your GitLab administrator has
After the NPM registry is enabled, it will be available for all new projects
by default. To enable it for existing projects, or if you want to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -63,7 +63,7 @@ This option is available only if your GitLab administrator has
After the NuGet Repository is enabled, it will be available for all new projects
by default. To enable it for existing projects, or if you want to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -28,7 +28,7 @@ This option is available only if your GitLab administrator has
After the PyPi Repository is enabled, it will be available for all new projects
by default. To enable it for existing projects, or if you want to disable it:
1. Navigate to your project's **Settings > General > Permissions**.
1. Navigate to your project's **Settings > General > Visibility, project features, permissions**.
1. Find the Packages feature and enable or disable it.
1. Click on **Save changes** for the changes to take effect.

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Changing Gitaly repository storage', :requires_admin do
shared_examples 'repository storage move' do
it 'confirms a `finished` status after moving project repository storage' do

View File

@ -4,7 +4,7 @@ require 'airborne'
require 'securerandom'
module QA
describe 'API basics' do
RSpec.describe 'API basics' do
before(:context) do
@api_client = Runtime::API::Client.new(:gitlab)
end

View File

@ -5,7 +5,7 @@ require 'securerandom'
require 'digest'
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Compare archives of different user projects with the same name and check they\'re different' do
include Support::Api

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
context 'Gitaly' do
describe 'High Availability', :orchestrated, :gitaly_ha do
let(:project) do

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
include Support::Api
describe 'Jira integration', :jira, :orchestrated, :requires_admin do

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Create a new merge request' do
before do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Merge request creation from fork' do
it 'user forks a project, submits a merge request and maintainer merges it' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create', quarantine: { issue: 'https://gitlab.com/gitlab-org/gitlab/-/issues/30226', type: :bug } do
RSpec.describe 'Create', quarantine: { issue: 'https://gitlab.com/gitlab-org/gitlab/-/issues/30226', type: :bug } do
describe 'Merge request rebasing' do
it 'user rebases source branch of merge request' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Merge request squashing' do
it 'user squashes commits while merging' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Download merge request patch and diff' do
before(:context) do
@merge_request = Resource::MergeRequest.fabricate_via_api! do |merge_request|

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'File templates' do
include Runtime::Fixtures

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Create, list, and delete branches via web' do
master_branch = 'master'
second_branch = 'second-branch'

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'SSH keys support' do
let(:key_title) { "key for ssh tests #{Time.now.to_f}" }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Git clone over HTTP', :ldap_no_tls do
before(:all) do
@project = Resource::Project.fabricate_via_api! do |scenario|

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Files management' do
it 'user creates, edits and deletes a file via the Web' do
Runtime::Browser.visit(:gitlab, Page::Main::Login)

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create', quarantine: { issue: 'https://gitlab.com/gitlab-org/gitlab/-/issues/217002', type: :investigating } do
RSpec.describe 'Create', quarantine: { issue: 'https://gitlab.com/gitlab-org/gitlab/-/issues/217002', type: :investigating } do
describe 'Gitaly repository storage', :orchestrated, :repository_storage, :requires_admin do
let(:user) { Resource::User.fabricate_or_use(Runtime::Env.gitlab_qa_username_1, Runtime::Env.gitlab_qa_password_1) }
let(:parent_project) do

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Push over HTTP using Git protocol version 2', :requires_git_protocol_v2 do
it 'user pushes to the repository' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Push over SSH using Git protocol version 2', :requires_git_protocol_v2 do
# Note: If you run this test against GDK make sure you've enabled sshd and
# enabled setting the Git protocol by adding `AcceptEnv GIT_PROTOCOL` to

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Git push over HTTP', :ldap_no_tls do
it 'user using a personal access token pushes code to the repository' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Push mirror a repository over HTTP' do
it 'configures and syncs a (push) mirrored repository' do
Runtime::Browser.visit(:gitlab, Page::Main::Login)

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create', :requires_admin do
RSpec.describe 'Create', :requires_admin do
describe 'push after setting the file size limit via admin/application_settings' do
# Note: The file size limits in this test should be greater than the limits in
# ee/browser_ui/3_create/repository/push_rules_spec to prevent that test from

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Git push over HTTP', :ldap_no_tls do
it 'user pushes code to the repository' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Protected branch support', :ldap_no_tls do
let(:branch_name) { 'protected-branch' }
let(:commit_message) { 'Protected push commit message' }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'SSH key support' do
# Note: If you run this test against GDK make sure you've enabled sshd
# See: https://gitlab.com/gitlab-org/gitlab-qa/blob/master/docs/run_qa_against_gdk.md

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Commit data' do
before(:context) do
# Get the user's details to confirm they're included in the email patch

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Version control for personal snippets' do
let(:new_file) { 'new_snippet_file' }
let(:changed_content) { 'changes' }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Version control for project snippets' do
let(:new_file) { 'new_snippet_file' }
let(:changed_content) { 'changes' }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create', :smoke do
RSpec.describe 'Create', :smoke do
describe 'Personal snippet creation' do
it 'User creates a personal snippet' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do # to be converted to a smoke test once proved to be stable
RSpec.describe 'Create' do # to be converted to a smoke test once proved to be stable
describe 'Project snippet creation' do
it 'User creates a project snippet' do
Flow::Login.sign_in

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Web IDE file templates' do
include Runtime::Fixtures

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'First file using Web IDE' do
let(:project) do
Resource::Project.fabricate_via_api! do |project|

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
describe 'Review a merge request in Web IDE' do
let(:new_file) { 'awesome_new_file.txt' }
let(:original_text) { 'Text' }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
context 'Wiki' do
describe 'testing wiki content creation inside a project' do
let(:new_wiki_title) { "just_another_wiki_page" }

View File

@ -1,7 +1,7 @@
# frozen_string_literal: true
module QA
context 'Create' do
RSpec.describe 'Create' do
context 'Wiki' do
describe 'testing wiki content manipulation inside a project' do
let(:new_wiki_title) { "just_another_wiki_page" }