diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/ci/pipelines.md | 12 | ||||
| -rw-r--r-- | doc/user/admin_area/settings/continuous_integration.md | 32 | ||||
| -rw-r--r-- | doc/user/group/index.md | 5 | ||||
| -rw-r--r-- | doc/user/project/img/issue_boards_multi_select.png | bin | 0 -> 21091 bytes | |||
| -rw-r--r-- | doc/user/project/issue_board.md | 12 | ||||
| -rw-r--r-- | doc/user/project/pipelines/settings.md | 5 |
6 files changed, 40 insertions, 26 deletions
diff --git a/doc/ci/pipelines.md b/doc/ci/pipelines.md index da67df3e774..0d0a40aceaa 100644 --- a/doc/ci/pipelines.md +++ b/doc/ci/pipelines.md @@ -436,15 +436,3 @@ To illustrate its life cycle: even if the commit history of the `example` branch has been overwritten by force-push. 1. GitLab Runner fetches the persistent pipeline ref and gets source code from the checkout-SHA. 1. When the pipeline finished, its persistent ref is cleaned up in a background process. - -NOTE: **NOTE**: At this moment, this feature is off dy default and can be manually enabled -by enabling `depend_on_persistent_pipeline_ref` feature flag, however, we'd remove this -feature flag and make it enabled by deafult by the day we release 12.4 _if we don't find any issues_. -If you'd be interested in manually turning on this behavior, please ask the administrator -to execute the following commands in rails console. - -```shell -> sudo gitlab-rails console # Login to Rails console of GitLab instance. -> project = Project.find_by_full_path('namespace/project-name') # Get the project instance. -> Feature.enable(:depend_on_persistent_pipeline_ref, project) # Enable the feature flag. -``` diff --git a/doc/user/admin_area/settings/continuous_integration.md b/doc/user/admin_area/settings/continuous_integration.md index ca2a0127ede..9b07ca13eee 100644 --- a/doc/user/admin_area/settings/continuous_integration.md +++ b/doc/user/admin_area/settings/continuous_integration.md @@ -29,26 +29,30 @@ If you want to disable it for a specific project, you can do so in ## Maximum artifacts size **(CORE ONLY)** The maximum size of the [job artifacts](../../../administration/job_artifacts.md) -can be set at the project level, group level, and at the instance level. The value is in *MB* and -the default is 100MB per job; on GitLab.com it's [set to 1G](../../gitlab_com/index.md#gitlab-cicd). +can be set at the project level, group level, and at the instance level. The value is: -To change it at the instance level: +- In *MB* and the default is 100MB per job. +- [Set to 1G](../../gitlab_com/index.md#gitlab-cicd) on GitLab.com. -1. Go to **Admin area > Settings > Continuous Integration and Deployment**. -1. Change the value of maximum artifacts size (in MB). -1. Hit **Save changes** for the changes to take effect. +To change it at the: -at the group level (this will override the instance setting): +- Instance level: -1. Go to **Group > Settings > CI / CD > General Pipelines**. -1. Change the value of maximum artifacts size (in MB). -1. Hit **Save changes** for the changes to take effect. + 1. Go to **Admin area > Settings > Continuous Integration and Deployment**. + 1. Change the value of maximum artifacts size (in MB). + 1. Hit **Save changes** for the changes to take effect. -at the project level (this will override the instance and group settings): +- [Group level](../../group/index.md#group-settings) (this will override the instance setting): -1. Go to **Project > Settings > CI / CD > General Pipelines**. -1. Change the value of maximum artifacts size (in MB). -1. Hit **Save changes** for the changes to take effect. + 1. Go to the group's **Settings > CI / CD > General Pipelines**. + 1. Change the value of **maximum artifacts size (in MB)**. + 1. Press **Save changes** for the changes to take effect. + +- [Project level](../../project/pipelines/settings.md) (this will override the instance and group settings): + + 1. Go to the project's **Settings > CI / CD > General Pipelines**. + 1. Change the value of **maximum artifacts size (in MB)**. + 1. Press **Save changes** for the changes to take effect. ## Default artifacts expiration **(CORE ONLY)** diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 258f1264b48..93ad32b3e45 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -451,6 +451,11 @@ For performance reasons, we may delay the update up to 1 hour and 30 minutes. If your namespace shows `N/A` as the total storage usage, you can trigger a recalculation by pushing a commit to any project in that namespace. +### Maximum artifacts size **(CORE ONLY)** + +For information about setting a maximum artifact size for a group, see +[Maximum artifacts size](../admin_area/settings/continuous_integration.md#maximum-artifacts-size-core-only). + ## User contribution analysis **(STARTER)** With [GitLab Contribution Analytics](contribution_analytics/index.md), diff --git a/doc/user/project/img/issue_boards_multi_select.png b/doc/user/project/img/issue_boards_multi_select.png Binary files differnew file mode 100644 index 00000000000..34ec0c1c58e --- /dev/null +++ b/doc/user/project/img/issue_boards_multi_select.png diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md index 0c0068ddd09..e9a7a15b630 100644 --- a/doc/user/project/issue_board.md +++ b/doc/user/project/issue_board.md @@ -180,6 +180,18 @@ These are shortcuts to your last 4 visited boards. When you're revisiting an issue board in a project or group with multiple boards, GitLab will automatically load the last board you visited. +### Multi-select Issue Cards + +As the name suggest, multi-select issue cards allows more than one issue card +to be dragged and dropped across different lists. This becomes helpful while +moving and grooming a lot of issues at once. + +You can multi-select an issue card by pressing `CTRL` + `Left mouse click` on +Windows or `CMD` + `Left mouse click` on MacOS. Once done, start by dragging one +of the issue card you have selected and drop it in the new list you want. + + + ### Configurable Issue Boards **(STARTER)** > Introduced in [GitLab Starter Edition 10.2](https://about.gitlab.com/2017/11/22/gitlab-10-2-released/#issue-boards-configuration). diff --git a/doc/user/project/pipelines/settings.md b/doc/user/project/pipelines/settings.md index 7b708a03b50..59e04907e21 100644 --- a/doc/user/project/pipelines/settings.md +++ b/doc/user/project/pipelines/settings.md @@ -60,6 +60,11 @@ if the job surpasses the threshold, it is marked as failed. Project defined timeout (either specific timeout set by user or the default 60 minutes timeout) may be [overridden on Runner level](../../../ci/runners/README.html#setting-maximum-job-timeout-for-a-runner). +## Maximum artifacts size **(CORE ONLY)** + +For information about setting a maximum artifact size for a project, see +[Maximum artifacts size](../../admin_area/settings/continuous_integration.md#maximum-artifacts-size-core-only). + ## Custom CI config path > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12509) in GitLab 9.4. |
