kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add latest changes from gitlab-org/gitlab@master

This commit is contained in:
GitLab Bot 2021-05-31 03:10:48 +00:00
parent 5d64bc743d
commit 5fa401a99e
10 changed files with 30 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
app/assets/stylesheets/page_bundles/pipelines.scss
View File

@ -116,7 +116,7 @@
position: absolute;
right: -7px;
top: 11px;
border-bottom: 2px solid $border-color;
border-bottom: 2px solid var(--border-color, $border-color);
}
}

2
doc/api/jobs.md
View File

@ -4,7 +4,7 @@ group: Pipeline Execution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Jobs API
# Jobs API **(FREE)**
## List project jobs

4
doc/api/lint.md
View File

@ -4,12 +4,10 @@ group: Pipeline Execution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# CI Lint API
# CI Lint API **(FREE)**
## Validate the CI YAML configuration
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5953) in GitLab 8.12.
Checks if CI/CD YAML configuration is valid. This endpoint validates basic CI/CD
configuration syntax. It doesn't have any namespace specific context.

4
doc/api/pipeline_schedules.md
View File

@ -4,7 +4,7 @@ group: Pipeline Execution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Pipeline schedules API
# Pipeline schedules API **(FREE)**
You can read more about [pipeline schedules](../ci/pipelines/schedules.md).
@ -317,8 +317,6 @@ Example response:
## Pipeline schedule variables
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/34518) in GitLab 10.0.
## Create a new pipeline schedule variable
Create a new variable of a pipeline schedule.

2
doc/api/pipeline_triggers.md
View File

@ -4,7 +4,7 @@ group: Pipeline Execution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Pipeline triggers API
# Pipeline triggers API **(FREE)**
You can read more about [triggering pipelines through the API](../ci/triggers/README.md).

12
doc/api/pipelines.md
View File

@ -4,7 +4,7 @@ group: Pipeline Execution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
---
# Pipelines API
# Pipelines API **(FREE)**
## Single Pipeline Requests
@ -23,8 +23,6 @@ Read more on [pagination](README.md#pagination).
## List project pipelines
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5837) in GitLab 8.11
```plaintext
GET /projects/:id/pipelines
```
@ -77,8 +75,6 @@ Example of response
## Get a single pipeline
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5837) in GitLab 8.11
```plaintext
GET /projects/:id/pipelines/:pipeline_id
```
@ -213,8 +209,6 @@ Sample response:
## Create a new pipeline
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7209) in GitLab 8.14
```plaintext
POST /projects/:id/pipeline
```
@ -263,8 +257,6 @@ Example of response
## Retry jobs in a pipeline
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5837) in GitLab 8.11
```plaintext
POST /projects/:id/pipelines/:pipeline_id/retry
```
@ -312,8 +304,6 @@ Response:
## Cancel a pipeline's jobs
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5837) in GitLab 8.11
```plaintext
POST /projects/:id/pipelines/:pipeline_id/cancel
```

9
doc/ci/pipelines/index.md
View File

@ -147,10 +147,11 @@ The pipeline now executes the jobs as configured.
> [Introduced in](https://gitlab.com/gitlab-org/gitlab/-/issues/30101) GitLab 13.7.
You can use the [`value` and `description`](../yaml/README.md#prefill-variables-in-manual-pipelines)
keywords to define [variables](../variables/README.md) that are prefilled when running
a pipeline manually.
keywords to define
[pipeline-level (global) variables](../variables/README.md#create-a-custom-cicd-variable-in-the-gitlab-ciyml-file)
that are prefilled when running a pipeline manually.
In pipelines triggered manually, the **Run pipelines** page displays all variables
In pipelines triggered manually, the **Run pipelines** page displays all top-level variables
with a `description` and `value` defined in the `.gitlab-ci.yml` file. The values
can then be modified if needed, which overrides the value for that single pipeline run.
@ -164,6 +165,8 @@ variables:
description: "The deployment target. Change this variable to 'canary' or 'production' if needed."
```
You cannot set job-level variables to be pre-filled when you run a pipeline manually.
### Run a pipeline by using a URL query string
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/24146) in GitLab 12.5.

4
doc/ci/yaml/README.md
View File

@ -4781,7 +4781,7 @@ You can use [YAML anchors for variables](#yaml-anchors-for-variables).
> [Introduced in](https://gitlab.com/gitlab-org/gitlab/-/issues/30101) GitLab 13.7.
Use the `value` and `description` keywords to define [variables that are prefilled](../pipelines/index.md#prefill-variables-in-manual-pipelines)
Use the `value` and `description` keywords to define [pipeline-level (global) variables that are prefilled](../pipelines/index.md#prefill-variables-in-manual-pipelines)
when [running a pipeline manually](../pipelines/index.md#run-a-pipeline-manually):
```yaml
@ -4791,6 +4791,8 @@ variables:
description: "The deployment target. Change this variable to 'canary' or 'production' if needed."
```
You cannot set job-level variables to be pre-filled when you run a pipeline manually.
### Configure runner behavior with variables
You can use [CI/CD variables](../variables/README.md) to configure how the runner processes Git requests:

13
doc/user/profile/account/two_factor_authentication.md
View File

@ -505,7 +505,18 @@ Feature.disable(:webauthn)
If you are receiving an `invalid pin code` error, this may indicate that there is a time sync issue between the authentication application and the GitLab instance itself.
Most authentication apps have a feature in the settings for syncing the time for the codes themselves. For Google Authenticator for example, go to `Settings > Time correction for codes`.
To avoid the time sync issue, enable time synchronization in the device that generates the codes. For example:
- For Android (Google Authenticator):
1. Go to the Main Menu in Google Authenticator.
1. Select Settings.
1. Select the Time correction for the codes.
1. Select Sync now.
- For iOS:
1. Go to Settings.
1. Select General.
1. Select Date & Time.
1. Enable Set Automatically. If it’s already enabled, disable it, wait a few seconds, and re-enable.
<!-- ## Troubleshooting

9
qa/qa/specs/features/browser_ui/4_verify/pipeline/create_and_process_pipeline_spec.rb
View File

@ -22,16 +22,13 @@ module QA
end
end
before do
Runtime::Feature.enable(feature_flag, project: project)
end
after do
runner.remove_via_api!
Runtime::Feature.disable(feature_flag, project: project)
end
it 'users creates a pipeline which gets processed', :smoke, testcase: 'https://gitlab.com/gitlab-org/quality/testcases/-/issues/1849' do
tags_mismatch_status = Runtime::Feature.enabled?(feature_flag, project: project) ? :failed : :pending
Flow::Login.sign_in
Resource::Repository::Commit.fabricate_via_api! do |commit|
@ -77,7 +74,7 @@ module QA
{
'test-success': :passed,
'test-failure': :failed,
'test-tags-mismatch': :failed,
'test-tags-mismatch': tags_mismatch_status,
'test-artifacts': :passed
}.each do |job, status|
Page::Project::Pipeline::Show.perform do |pipeline|