diff --git a/.gitlab/ci/rules.gitlab-ci.yml b/.gitlab/ci/rules.gitlab-ci.yml index 82cd1be6bd3..276d539378c 100644 --- a/.gitlab/ci/rules.gitlab-ci.yml +++ b/.gitlab/ci/rules.gitlab-ci.yml @@ -47,9 +47,6 @@ .if-merge-request-approved: &if-merge-request-approved if: '($CI_MERGE_REQUEST_EVENT_TYPE == "merged_result" || $CI_MERGE_REQUEST_EVENT_TYPE == "detached") && $CI_MERGE_REQUEST_LABELS =~ /pipeline:mr-approved/' -.if-merge-request-approved-and-specific-devops-stage: &if-merge-request-approved-and-specific-devops-stage - if: '($CI_MERGE_REQUEST_EVENT_TYPE == "merged_result" || $CI_MERGE_REQUEST_EVENT_TYPE == "detached") && ($CI_MERGE_REQUEST_LABELS =~ /pipeline:mr-approved/ && $CI_MERGE_REQUEST_LABELS =~ /devops::(create|govern|manage|plan|verify|package|monitor|data stores|fulfillment|systems)/)' - .if-merge-request-and-specific-devops-stage: &if-merge-request-and-specific-devops-stage if: '($CI_MERGE_REQUEST_EVENT_TYPE == "merged_result" || $CI_MERGE_REQUEST_EVENT_TYPE == "detached") && $CI_MERGE_REQUEST_LABELS =~ /devops::(create|govern|manage|plan|verify|package|monitor|data stores|fulfillment|systems)/' @@ -1473,6 +1470,17 @@ - <<: *if-foss-schedule - <<: *if-merge-request-labels-update-caches +.qa:rules:code-merge-request: + rules: + - <<: *if-merge-request + changes: *code-patterns + +.qa:rules:code-merge-request-allowed-to-fail: + rules: + - <<: *if-merge-request + changes: *code-patterns + allow_failure: true + .qa:rules:code-merge-request-manual: rules: - <<: *if-merge-request @@ -1480,11 +1488,6 @@ when: manual allow_failure: true -.qa:rules:code-merge-request: - rules: - - <<: *if-merge-request - changes: *code-patterns - .qa:rules:internal: rules: - if: '$ENABLE_QA_INTERNAL == "true"' @@ -1541,6 +1544,8 @@ - <<: *if-merge-request-targeting-stable-branch changes: *setup-test-env-patterns - <<: *if-ruby-branch + - <<: *if-merge-request + changes: *qa-patterns - <<: *if-merge-request changes: *dependency-patterns variables: @@ -1554,16 +1559,14 @@ changes: *nodejs-patterns - <<: *if-merge-request changes: *ci-qa-patterns - - <<: *if-merge-request - changes: *qa-patterns - <<: *if-dot-com-gitlab-org-and-security-merge-request-and-qa-tests-specified changes: *code-patterns - <<: *if-force-ci + - <<: *if-merge-request-and-specific-devops-stage + changes: *code-patterns # From .qa:rules:package-and-test-schedule - <<: *if-dot-com-gitlab-org-schedule - # From .qa:rules:code-merge-request-manual - - <<: *if-merge-request - changes: *code-patterns + - !reference [".qa:rules:code-merge-request", rules] .qa:rules:package-and-test-never-run: rules: @@ -1582,6 +1585,13 @@ allow_failure: true - <<: *if-ruby-branch allow_failure: true + # Run tests automatically for MRs that touch QA files + - <<: *if-merge-request + changes: *qa-patterns + allow_failure: true + # Otherwise, only run tests after the MR is approved + - <<: *if-merge-request-not-approved + when: never - <<: *if-merge-request changes: *dependency-patterns variables: @@ -1600,16 +1610,13 @@ - <<: *if-merge-request changes: *ci-qa-patterns allow_failure: true - - <<: *if-merge-request - changes: *qa-patterns - allow_failure: true - <<: *if-dot-com-gitlab-org-and-security-merge-request-and-qa-tests-specified changes: *code-patterns allow_failure: true - <<: *if-force-ci when: manual allow_failure: true - - <<: *if-merge-request-approved-and-specific-devops-stage + - <<: *if-merge-request-and-specific-devops-stage changes: *code-patterns allow_failure: true # We used to have a rule at the end here that would catch any remaining code MRs and allow the job to be run @@ -1744,7 +1751,7 @@ # These are based on `.qa:rules:trigger-omnibus` except: # 1. Automatic jobs changed to `when: never.` -# 2. For specific devops stage, do not run for code-patterns +# 2. Do not run for specific devops stage # If any changes are made to this rule, `.qa:rules:follow-up-e2e` should also be updated. .qa:rules:manual-omnibus-and-follow-up-e2e: rules: @@ -1759,9 +1766,7 @@ - !reference [".qa:rules:package-and-test-never-run", rules] - <<: *if-merge-request-and-specific-devops-stage when: never - - <<: *if-merge-request - changes: *code-patterns - allow_failure: true + - !reference [".qa:rules:code-merge-request-allowed-to-fail", rules] # These are based on `qa:rules:package-and-test-ee` but with when:never in all except for code-patterns in merge requests .qa:rules:post-run-e2e-message: @@ -1806,10 +1811,7 @@ # Do not run on unapproved MR - <<: *if-merge-request-not-approved when: never - # From .qa:rules:code-merge-request-manual - - <<: *if-merge-request - changes: *code-patterns - allow_failure: true + - !reference [".qa:rules:code-merge-request-allowed-to-fail", rules] .qa:rules:fulfillment-e2e-quarantine-report: rules: diff --git a/app/assets/javascripts/groups/settings/api/access_dropdown_api.js b/app/assets/javascripts/groups/settings/api/access_dropdown_api.js index 37f95a7ab30..e232b1977f0 100644 --- a/app/assets/javascripts/groups/settings/api/access_dropdown_api.js +++ b/app/assets/javascripts/groups/settings/api/access_dropdown_api.js @@ -7,15 +7,16 @@ const buildUrl = (urlRoot, url) => { return joinPaths(urlRoot, url); }; -const defaultOptions = { includeParentDescendants: false }; +const defaultOptions = { includeParentDescendants: false, includeParentSharedGroups: false }; export const getSubGroups = (options = defaultOptions) => { - const { includeParentDescendants } = options; + const { includeParentDescendants, includeParentSharedGroups } = options; return axios.get(buildUrl(gon.relative_url_root || '', GROUP_SUBGROUPS_PATH), { params: { group_id: gon.current_group_id, include_parent_descendants: includeParentDescendants, + include_parent_shared_groups: includeParentSharedGroups, }, }); }; diff --git a/app/assets/javascripts/groups/settings/components/access_dropdown.vue b/app/assets/javascripts/groups/settings/components/access_dropdown.vue index fee1383c8e2..327f73b88c2 100644 --- a/app/assets/javascripts/groups/settings/components/access_dropdown.vue +++ b/app/assets/javascripts/groups/settings/components/access_dropdown.vue @@ -96,7 +96,7 @@ export default { Promise.all([ this.groups.length ? Promise.resolve({ data: this.groups }) - : getSubGroups({ includeParentDescendants: true }), + : getSubGroups({ includeParentDescendants: true, includeParentSharedGroups: true }), ]) .then(([groupsResponse]) => { this.consolidateData(groupsResponse.data); diff --git a/app/assets/javascripts/groups_projects/components/more_actions_dropdown.vue b/app/assets/javascripts/groups_projects/components/more_actions_dropdown.vue index 88634816177..fb5370c7ce2 100644 --- a/app/assets/javascripts/groups_projects/components/more_actions_dropdown.vue +++ b/app/assets/javascripts/groups_projects/components/more_actions_dropdown.vue @@ -29,6 +29,8 @@ export default { 'withdrawPath', 'withdrawConfirmMessage', 'requestAccessPath', + 'canEdit', + 'editPath', ], computed: { namespaceType() { @@ -37,6 +39,9 @@ export default { hasPath() { return this.leavePath || this.withdrawPath || this.requestAccessPath; }, + settingsTitle() { + return this.isGroup ? this.$options.i18n.groupSettings : this.$options.i18n.projectSettings; + }, leaveTitle() { return this.isGroup ? this.$options.i18n.groupLeaveTitle @@ -99,6 +104,15 @@ export default { }, }; }, + settingsItem() { + return { + text: this.settingsTitle, + href: this.editPath, + extraAttrs: { + 'data-testid': `settings-${this.namespaceType}-link`, + }, + }; + }, }, i18n: { actionsLabel: __('Actions'), @@ -110,6 +124,8 @@ export default { requestAccessTitle: __('Request Access'), groupCopyTitle: s__('GroupPage|Copy group ID: %{id}'), projectCopyTitle: s__('ProjectPage|Copy project ID: %{id}'), + projectSettings: s__('ProjectPage|Project settings'), + groupSettings: s__('GroupPage|Group settings'), }, }; @@ -153,6 +169,7 @@ export default { :item="copyIdItem" :data-clipboard-text="groupOrProjectId" /> + diff --git a/app/assets/javascripts/groups_projects/init_more_actions_dropdown.js b/app/assets/javascripts/groups_projects/init_more_actions_dropdown.js index c5f6d29d080..7a1b1bfc535 100644 --- a/app/assets/javascripts/groups_projects/init_more_actions_dropdown.js +++ b/app/assets/javascripts/groups_projects/init_more_actions_dropdown.js @@ -17,6 +17,8 @@ export default function InitMoreActionsDropdown() { withdrawPath, withdrawConfirmMessage, requestAccessPath, + canEdit, + editPath, } = el.dataset; return new Vue({ @@ -30,6 +32,8 @@ export default function InitMoreActionsDropdown() { withdrawPath, withdrawConfirmMessage, requestAccessPath, + canEdit: parseBoolean(canEdit), + editPath, }, render: (createElement) => createElement(MoreActionsDropdown), }); diff --git a/app/assets/javascripts/pages/projects/home_panel/index.js b/app/assets/javascripts/pages/projects/home_panel/index.js index 071d3d81b7e..82c49c055ad 100644 --- a/app/assets/javascripts/pages/projects/home_panel/index.js +++ b/app/assets/javascripts/pages/projects/home_panel/index.js @@ -33,6 +33,8 @@ const initHomePanel = () => { requestAccessPath, withdrawConfirmMessage, withdrawPath, + canEdit, + editPath, // Fork component canCreateFork, @@ -75,6 +77,8 @@ const initHomePanel = () => { requestAccessPath, withdrawConfirmMessage, withdrawPath, + canEdit, + editPath, // Fork component canCreateFork: parseBoolean(canCreateFork), diff --git a/app/assets/javascripts/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit.vue b/app/assets/javascripts/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit.vue index 45ea5642518..7f7470305e5 100644 --- a/app/assets/javascripts/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit.vue +++ b/app/assets/javascripts/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit.vue @@ -88,6 +88,11 @@ export default { required: false, default: false, }, + clearSearchOnItemSelect: { + type: Boolean, + required: false, + default: false, + }, }, data() { return { @@ -131,6 +136,13 @@ export default { } else { this.isDirty = true; this.$emit('updateSelected', this.localSelectedItem); + this.clearSearch(); + } + }, + clearSearch() { + if (this.clearSearchOnItemSelect) { + this.setSearchKey(''); + this.$refs.listbox.$refs.searchBox.clearInput(); } }, onListboxShown() { @@ -185,6 +197,7 @@ export default { { with_status(:manual) } scope :scheduled, -> { with_status(:scheduled) } scope :alive, -> { with_status(*ALIVE_STATUSES) } - scope :alive_or_scheduled, -> { with_status(*klass::CANCELABLE_STATUSES) } scope :created_or_pending, -> { with_status(:created, :pending) } scope :running_or_pending, -> { with_status(:running, :pending) } scope :finished, -> { with_status(:success, :failed, :canceled) } diff --git a/app/models/group.rb b/app/models/group.rb index d8fc468e734..80fcd4470a0 100644 --- a/app/models/group.rb +++ b/app/models/group.rb @@ -239,6 +239,27 @@ class Group < Namespace .where(group_group_links: { shared_group_id: group.self_and_ancestors }) end + # Returns all groups that are shared with the given group (see :shared_with_group) + # and all descendents of the given group + # returns none if the given group is nil + scope :descendants_with_shared_with_groups, -> (group) do + return none if group.nil? + + descendants_query = group.descendants.select(:id) + # since we're only interested in ids, we query GroupGroupLink directly instead of using :shared_with_group + # to avoid an extra JOIN in the resulting query + shared_groups_query = GroupGroupLink + .where(shared_group_id: group.id) + .select('shared_with_group_id AS id') + + combined_query = Group + .from_union(descendants_query, shared_groups_query, alias_as: :combined) + .unscope(where: :type) + .select(:id) + + id_in(combined_query) + end + # WARNING: This method should never be used on its own # please do make sure the number of rows you are filtering is small # enough for this query diff --git a/app/services/ci/pipeline_creation/cancel_redundant_pipelines_service.rb b/app/services/ci/pipeline_creation/cancel_redundant_pipelines_service.rb index 46cc08f6063..4042f536922 100644 --- a/app/services/ci/pipeline_creation/cancel_redundant_pipelines_service.rb +++ b/app/services/ci/pipeline_creation/cancel_redundant_pipelines_service.rb @@ -67,7 +67,7 @@ module Ci def parent_and_child_pipelines(ids) Ci::Pipeline.object_hierarchy(parent_auto_cancelable_pipelines(ids), project_condition: :same) .base_and_descendants - .alive_or_scheduled + .cancelable end def auto_cancel_pipelines(pipeline_ids) diff --git a/app/services/work_items/callbacks/time_tracking.rb b/app/services/work_items/callbacks/time_tracking.rb index b33b128f3d4..917fe101d1f 100644 --- a/app/services/work_items/callbacks/time_tracking.rb +++ b/app/services/work_items/callbacks/time_tracking.rb @@ -7,14 +7,50 @@ module WorkItems if excluded_in_new_type? params.delete(:time_estimate) params.delete(:spend_time) + params.delete(:timelog) end return unless has_permission?(:admin_work_item) - return if !params.present? || (!params.key?(:time_estimate) && !params.key?(:spend_time)) + # below 2 parse_*_data methods, parse the data coming in from `time_tracking_widget` argument, in + # work item update mutation. + parse_timelog_data if params.key?(:timelog) && !params[:spend_time] + parse_time_estimate_data if params.key?(:time_estimate) && params[:time_estimate].is_a?(String) + + # we still need to set the data here, in case when we had no data coming in from the `time_tracking_widget` + # argument, but data was still set through updating the description and using quick actions. work_item.time_estimate = params[:time_estimate] if params[:time_estimate].present? work_item.spend_time = params[:spend_time] if params[:spend_time].present? end + + private + + def parse_timelog_data + time_spent = params.dig(:timelog, :time_spent) + parsed_time_spent = if time_spent == ":reset" + :reset + else + Gitlab::TimeTrackingFormatter.parse(time_spent) + end + + raise_error(invalid_time_spent_format('Time spent')) if parsed_time_spent.nil? + + params[:spend_time] = { duration: parsed_time_spent, user_id: current_user.id }.merge(params[:timelog]) + end + + def parse_time_estimate_data + params[:time_estimate] = begin + Integer(params[:time_estimate] || '') + rescue ArgumentError + parsed_time_estimate = Gitlab::TimeTrackingFormatter.parse(params[:time_estimate]) + raise_error(invalid_time_spent_format('Time estimate')) if parsed_time_estimate.nil? + parsed_time_estimate + end + end + + def invalid_time_spent_format(argument_name) + format(_("%{argument_name} must be formatted correctly. For example: 1h 30m."), argument_name: argument_name) + end end end end diff --git a/app/views/projects/_sidebar.html.haml b/app/views/projects/_sidebar.html.haml index 9564e84d8cc..7c7d2819bac 100644 --- a/app/views/projects/_sidebar.html.haml +++ b/app/views/projects/_sidebar.html.haml @@ -3,15 +3,7 @@ %aside.project-page-sidebar .project-page-sidebar-block.home-panel-home-desc.gl-py-4.gl-border-b.gl-border-gray-50{ class: 'gl-pt-2!' } - .gl-display-flex.gl-justify-content-space-between - %h2.gl-font-base.gl-font-weight-bold.gl-reset-line-height.gl-text-gray-900.gl-m-0.gl-mb-1= s_('ProjectPage|Project information') - -# Project settings - - if can?(current_user, :admin_project, @project) - = render Pajamas::ButtonComponent.new(href: edit_project_path(@project), - category: :tertiary, - icon: 'settings', - size: :small, - button_options: { class: 'has-tooltip gl-ml-2 gl-sm-mr-3', title: s_('ProjectPage|Project settings'), 'aria-label' => s_('ProjectPage|Project settings'), 'data-testid': 'project-settings-button' }) + %h2.gl-font-base.gl-font-weight-bold.gl-reset-line-height.gl-text-gray-900.gl-m-0.gl-mb-1= s_('ProjectPage|Project information') -# Project description - if @project.description.present? .home-panel-description.text-break diff --git a/db/docs/user_credit_card_validations.yml b/db/docs/user_credit_card_validations.yml index 4c8a851ade7..928d9ffc98d 100644 --- a/db/docs/user_credit_card_validations.yml +++ b/db/docs/user_credit_card_validations.yml @@ -7,4 +7,4 @@ feature_categories: description: Stores whether the user has completed a first time validation to run CI pipelines introduced_by_url: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60626 milestone: '13.12' -gitlab_schema: gitlab_main +gitlab_schema: gitlab_main_clusterwide diff --git a/doc/administration/admin_area.md b/doc/administration/admin_area.md index c9d35a10559..9bb7bef687f 100644 --- a/doc/administration/admin_area.md +++ b/doc/administration/admin_area.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Admin Area provides a web UI to manage and configure features of GitLab self-managed instances. If you are an administrator, to access the Admin Area: @@ -150,7 +150,7 @@ the identities being used for an account. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1772) in GitLab 13.8. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/292436) in GitLab 13.9. @@ -478,7 +478,7 @@ The content of each log file is listed in chronological order. To minimize perfo DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The **Audit Events** page lists changes made within the GitLab server. With this information you can control, analyze, and track every change. diff --git a/doc/administration/analytics/dev_ops_reports.md b/doc/administration/analytics/dev_ops_reports.md index 769fb0f99c2..d8bd1e9f7f5 100644 --- a/doc/administration/analytics/dev_ops_reports.md +++ b/doc/administration/analytics/dev_ops_reports.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed DevOps Reports give you an overview of your entire instance's adoption of [DevOps](https://about.gitlab.com/topics/devops/) @@ -45,7 +45,7 @@ feature is available. DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/247112) in GitLab 13.7 as a [Beta feature](../../policy/experiment-beta-support.md#beta). > - The Overview tab [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/330401) in GitLab 14.1. diff --git a/doc/administration/analytics/index.md b/doc/administration/analytics/index.md index bba526db559..44204796444 100644 --- a/doc/administration/analytics/index.md +++ b/doc/administration/analytics/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41416) in GitLab 11.2. diff --git a/doc/administration/analytics/usage_trends.md b/doc/administration/analytics/usage_trends.md index 3cf5fcec6a7..55330e26824 100644 --- a/doc/administration/analytics/usage_trends.md +++ b/doc/administration/analytics/usage_trends.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/235754) in GitLab 13.5 behind a feature flag, disabled by default. > - [Became enabled by default](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46962) in GitLab 13.6. diff --git a/doc/administration/appearance.md b/doc/administration/appearance.md index 914f71d151b..89a385b2263 100644 --- a/doc/administration/appearance.md +++ b/doc/administration/appearance.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can update your settings to change the look and feel of your GitLab self-managed instance. diff --git a/doc/administration/application_settings_cache.md b/doc/administration/application_settings_cache.md index 62cf4ead33a..3c1f8d88b2e 100644 --- a/doc/administration/application_settings_cache.md +++ b/doc/administration/application_settings_cache.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed By default, GitLab caches application settings for 60 seconds. Occasionally, you may need to increase that interval to have more delay between application diff --git a/doc/administration/audit_event_reports.md b/doc/administration/audit_event_reports.md index 4971555c4e9..73123595adf 100644 --- a/doc/administration/audit_event_reports.md +++ b/doc/administration/audit_event_reports.md @@ -73,7 +73,7 @@ Project audit events can also be accessed using the [Project Audit Events API](. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can view audit events from user actions across an entire GitLab instance. To view instance audit events: @@ -105,7 +105,7 @@ After upgrading to a paid tier, you can also see successful sign-in events on au DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1449) in GitLab 13.4. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/285441) in GitLab 13.7. @@ -154,7 +154,7 @@ All items are sorted by `created_at` in ascending order. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/536) in GitLab 13.0. > - Impersonation session events included in group audit events in GitLab 14.8. diff --git a/doc/administration/audit_event_streaming/graphql_api.md b/doc/administration/audit_event_streaming/graphql_api.md index 4dd7f4c3ad5..b5cb46cd991 100644 --- a/doc/administration/audit_event_streaming/graphql_api.md +++ b/doc/administration/audit_event_streaming/graphql_api.md @@ -570,7 +570,7 @@ Streaming configuration is deleted if: DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/335175) in GitLab 16.0 [with a flag](../feature_flags.md) named `ff_external_audit_events`. Disabled by default. > - [Feature flag `ff_external_audit_events`](https://gitlab.com/gitlab-org/gitlab/-/issues/393772) enabled by default in GitLab 16.2. diff --git a/doc/administration/audit_event_streaming/index.md b/doc/administration/audit_event_streaming/index.md index 1563ac4b56f..17856ebf24f 100644 --- a/doc/administration/audit_event_streaming/index.md +++ b/doc/administration/audit_event_streaming/index.md @@ -369,7 +369,7 @@ To delete AWS S3 streaming destinations to a top-level group: DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/398107) in GitLab 16.1 [with a flag](../feature_flags.md) named `ff_external_audit_events`. Disabled by default. > - [Feature flag `ff_external_audit_events`](https://gitlab.com/gitlab-org/gitlab/-/issues/393772) enabled by default in GitLab 16.2. diff --git a/doc/administration/auditor_users.md b/doc/administration/auditor_users.md index 0fffb53e674..df125858769 100644 --- a/doc/administration/auditor_users.md +++ b/doc/administration/auditor_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Users with auditor access have read-only access to all groups, projects, and other resources except: diff --git a/doc/administration/auth/atlassian.md b/doc/administration/auth/atlassian.md index b94bba7ce89..7c330934607 100644 --- a/doc/administration/auth/atlassian.md +++ b/doc/administration/auth/atlassian.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To enable the Atlassian OmniAuth provider for passwordless authentication you must register an application with Atlassian. diff --git a/doc/administration/auth/cognito.md b/doc/administration/auth/cognito.md index c6b986922a4..122031f4a9f 100644 --- a/doc/administration/auth/cognito.md +++ b/doc/administration/auth/cognito.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Amazon Web Services (AWS) Cognito lets you add user sign-up, sign-in, and access control to your GitLab instance. The following documentation enables AWS Cognito as an OAuth 2.0 provider. diff --git a/doc/administration/auth/crowd.md b/doc/administration/auth/crowd.md index 488096acd17..4d615ee4905 100644 --- a/doc/administration/auth/crowd.md +++ b/doc/administration/auth/crowd.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: This feature was [deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/369117) in GitLab 15.3 and is planned for diff --git a/doc/administration/auth/index.md b/doc/administration/auth/index.md index f6fcc0184ac..f95f8360629 100644 --- a/doc/administration/auth/index.md +++ b/doc/administration/auth/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab integrates with a number of [OmniAuth providers](../../integration/omniauth.md#supported-providers), and the following external authentication and authorization providers: diff --git a/doc/administration/auth/jwt.md b/doc/administration/auth/jwt.md index 5bd36b91d1e..a567e3b735b 100644 --- a/doc/administration/auth/jwt.md +++ b/doc/administration/auth/jwt.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To enable the JWT OmniAuth provider, you must register your application with JWT. JWT provides you with a secret key for you to use. diff --git a/doc/administration/auth/ldap/index.md b/doc/administration/auth/ldap/index.md index 067cd9df3eb..024278b2184 100644 --- a/doc/administration/auth/ldap/index.md +++ b/doc/administration/auth/ldap/index.md @@ -480,7 +480,7 @@ you must do so in an `attributes` hash. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed These LDAP sync configuration settings are optional, excluding `group_base` which required when `external_groups` is configured: @@ -496,7 +496,7 @@ required when `external_groups` is configured: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you have users on multiple LDAP servers, you can configure GitLab to use them. To add additional LDAP servers: diff --git a/doc/administration/auth/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md index f53170615c3..7617db1186d 100644 --- a/doc/administration/auth/ldap/ldap-troubleshooting.md +++ b/doc/administration/auth/ldap/ldap-troubleshooting.md @@ -61,7 +61,7 @@ main: # 'main' is the GitLab 'provider ID' of this LDAP server DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following allows you to perform a search in LDAP using the rails console. Depending on what you're trying to do, it may make more sense to query [a user](#query-a-user-in-ldap) @@ -260,7 +260,7 @@ ldapsearch -H ldaps://$host:$port -D "$bind_dn" -y bind_dn_password.txt -b "$ba DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The output from a manual [user sync](ldap_synchronization.md#user-sync) can show you what happens when GitLab tries to sync its users against LDAP. Enter the [rails console](#rails-console) @@ -278,7 +278,7 @@ Next, [learn how to read the output](#example-console-output-after-a-user-sync). DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The output from a [manual user sync](#sync-all-users) is very verbose, and a single user's successful sync can look like this: @@ -373,7 +373,7 @@ Gitlab::Auth::Ldap::Person.find_by_uid('', adapter) DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed #### Memberships not granted diff --git a/doc/administration/auth/oidc.md b/doc/administration/auth/oidc.md index 0418af2a0e7..a6d1de4fa3f 100644 --- a/doc/administration/auth/oidc.md +++ b/doc/administration/auth/oidc.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can use GitLab as a client application with [OpenID Connect](https://openid.net/specs/openid-connect-core-1_0.html) as an OmniAuth provider. @@ -940,7 +940,7 @@ based on group membership, configure GitLab to identify: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Your IdP must pass group information to GitLab in the OIDC response. To use this response to assign users as auditors based on group membership, configure GitLab to identify: diff --git a/doc/administration/auth/test_oidc_oauth.md b/doc/administration/auth/test_oidc_oauth.md index 586c8a85e85..39dfecc5c86 100644 --- a/doc/administration/auth/test_oidc_oauth.md +++ b/doc/administration/auth/test_oidc_oauth.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To test OIDC/OAuth in GitLab, you must: diff --git a/doc/administration/backup_restore/backup_gitlab.md b/doc/administration/backup_restore/backup_gitlab.md index 6877233279a..a66bb172565 100644 --- a/doc/administration/backup_restore/backup_gitlab.md +++ b/doc/administration/backup_restore/backup_gitlab.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The exact procedure for backing up GitLab depends on many factors. Your particular deployment's usage and configuration determine what kind of data exists, where it is located, and how much there is. These factors influence your options for how to perform a back up, how to store it, and how to restore it. diff --git a/doc/administration/backup_restore/backup_large_reference_architectures.md b/doc/administration/backup_restore/backup_large_reference_architectures.md index e91f307d481..1af8c7348de 100644 --- a/doc/administration/backup_restore/backup_large_reference_architectures.md +++ b/doc/administration/backup_restore/backup_large_reference_architectures.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document describes how to: diff --git a/doc/administration/backup_restore/index.md b/doc/administration/backup_restore/index.md index 669a6cde80b..c78decbdd28 100644 --- a/doc/administration/backup_restore/index.md +++ b/doc/administration/backup_restore/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Your software or organization depends on the data in your GitLab instance. You need to ensure this data is protected from adverse events such as: diff --git a/doc/administration/backup_restore/restore_gitlab.md b/doc/administration/backup_restore/restore_gitlab.md index 44a1404a26f..bd1e87b532c 100644 --- a/doc/administration/backup_restore/restore_gitlab.md +++ b/doc/administration/backup_restore/restore_gitlab.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab provides a command-line interface to restore your entire installation, and is flexible enough to fit your needs. diff --git a/doc/administration/broadcast_messages.md b/doc/administration/broadcast_messages.md index 79f9e5726e6..72291c6f84c 100644 --- a/doc/administration/broadcast_messages.md +++ b/doc/administration/broadcast_messages.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - Target roles [introduced](https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/461) in GitLab 14.8 [with a flag](../administration/feature_flags.md) named `role_targeted_broadcast_messages`. Disabled by default. > - Theme [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83251) and background color removed in GitLab 14.10. diff --git a/doc/administration/cicd.md b/doc/administration/cicd.md index df935f86cfb..5c99e2ed497 100644 --- a/doc/administration/cicd.md +++ b/doc/administration/cicd.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab administrators can manage the GitLab CI/CD configuration for their instance. @@ -65,7 +65,7 @@ For Linux package installations: DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The maximum number of jobs that can be defined in `needs` defaults to 50. diff --git a/doc/administration/clusters/kas.md b/doc/administration/clusters/kas.md index cdde443e6d6..462fb0be3fb 100644 --- a/doc/administration/clusters/kas.md +++ b/doc/administration/clusters/kas.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/3834) in GitLab 13.10, the GitLab agent server (KAS) became available on GitLab.com at `wss://kas.gitlab.com`. > - [Moved](https://gitlab.com/groups/gitlab-org/-/epics/6290) from GitLab Premium to GitLab Free in 14.5. diff --git a/doc/administration/compliance.md b/doc/administration/compliance.md index 273df7b7c90..afefb2fc5bd 100644 --- a/doc/administration/compliance.md +++ b/doc/administration/compliance.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab compliance features ensure your GitLab instance meets common compliance standards, and are available at various pricing tiers. For more information about compliance management, see the compliance management [solutions page](https://about.gitlab.com/solutions/compliance/). diff --git a/doc/administration/configure.md b/doc/administration/configure.md index caf7348a16b..7ea3b19ea33 100644 --- a/doc/administration/configure.md +++ b/doc/administration/configure.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Customize and configure your self-managed GitLab installation. diff --git a/doc/administration/consul.md b/doc/administration/consul.md index 3150f6614f9..252eb2b98ea 100644 --- a/doc/administration/consul.md +++ b/doc/administration/consul.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed A Consul cluster consists of both [server and client agents](https://developer.hashicorp.com/consul/docs/agent). diff --git a/doc/administration/credentials_inventory.md b/doc/administration/credentials_inventory.md index 422371679ef..b0fd268c64e 100644 --- a/doc/administration/credentials_inventory.md +++ b/doc/administration/credentials_inventory.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/20912) in GitLab 12.6. > - [Bot-created access tokens not displayed in personal access token list](https://gitlab.com/gitlab-org/gitlab/-/issues/351759) in GitLab 14.9. diff --git a/doc/administration/custom_project_templates.md b/doc/administration/custom_project_templates.md index 744d7cf82e7..7745d4500c2 100644 --- a/doc/administration/custom_project_templates.md +++ b/doc/administration/custom_project_templates.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed As an administrator, you can configure a group that contains projects available for use as the source of project templates on your instance. You can then diff --git a/doc/administration/diff_limits.md b/doc/administration/diff_limits.md index 055a984927a..a1a66d54798 100644 --- a/doc/administration/diff_limits.md +++ b/doc/administration/diff_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can set a maximum size for display of diff files (patches). diff --git a/doc/administration/docs_self_host.md b/doc/administration/docs_self_host.md index 7c19ee3103e..564208e01eb 100644 --- a/doc/administration/docs_self_host.md +++ b/doc/administration/docs_self_host.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you are not able to access the GitLab product documentation at `docs.gitlab.com`, you can host the documentation yourself instead. diff --git a/doc/administration/email_from_gitlab.md b/doc/administration/email_from_gitlab.md index 0834a801e55..e3ad383d1a7 100644 --- a/doc/administration/email_from_gitlab.md +++ b/doc/administration/email_from_gitlab.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Administrators can email all users, or users of a chosen group or project. Users receive the email at their primary email address. diff --git a/doc/administration/encrypted_configuration.md b/doc/administration/encrypted_configuration.md index f1a0cd4f7f4..f373f1ffcc7 100644 --- a/doc/administration/encrypted_configuration.md +++ b/doc/administration/encrypted_configuration.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/45712) in GitLab 13.7. diff --git a/doc/administration/environment_variables.md b/doc/administration/environment_variables.md index b2937bdedff..cf976dc2349 100644 --- a/doc/administration/environment_variables.md +++ b/doc/administration/environment_variables.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab exposes certain environment variables which can be used to override their defaults values. diff --git a/doc/administration/external_pipeline_validation.md b/doc/administration/external_pipeline_validation.md index 40afbdd9203..7f7a9f2f30e 100644 --- a/doc/administration/external_pipeline_validation.md +++ b/doc/administration/external_pipeline_validation.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can use an external service to validate a pipeline before it's created. diff --git a/doc/administration/external_users.md b/doc/administration/external_users.md index 72625b6d6e4..d35e11ef18b 100644 --- a/doc/administration/external_users.md +++ b/doc/administration/external_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed In cases where it is desired that a user has access only to some internal or private projects, there is the option of creating **External Users**. This diff --git a/doc/administration/file_hooks.md b/doc/administration/file_hooks.md index e07e6b03ed3..eb7ab7bcca8 100644 --- a/doc/administration/file_hooks.md +++ b/doc/administration/file_hooks.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Use custom file hooks (not to be confused with [server hooks](server_hooks.md) or [system hooks](system_hooks.md)), to introduce custom integrations without modifying the GitLab source code. diff --git a/doc/administration/geo/disaster_recovery/background_verification.md b/doc/administration/geo/disaster_recovery/background_verification.md index c100ff79222..a0821344cab 100644 --- a/doc/administration/geo/disaster_recovery/background_verification.md +++ b/doc/administration/geo/disaster_recovery/background_verification.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Automatic background verification ensures that the transferred data matches a calculated checksum. If the checksum of the data on the **primary** site matches checksum of the diff --git a/doc/administration/geo/disaster_recovery/bring_primary_back.md b/doc/administration/geo/disaster_recovery/bring_primary_back.md index 1a85374105e..dcbfbd7c990 100644 --- a/doc/administration/geo/disaster_recovery/bring_primary_back.md +++ b/doc/administration/geo/disaster_recovery/bring_primary_back.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed After a failover, it is possible to fail back to the demoted **primary** site to restore your original configuration. This process consists of two steps: diff --git a/doc/administration/geo/disaster_recovery/index.md b/doc/administration/geo/disaster_recovery/index.md index 41b5d09d98e..a0352f4248c 100644 --- a/doc/administration/geo/disaster_recovery/index.md +++ b/doc/administration/geo/disaster_recovery/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Geo replicates your database, your Git repositories, and few other assets, but there are some [limitations](../index.md#limitations). diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md index 604fb06cb60..8597bdec79b 100644 --- a/doc/administration/geo/disaster_recovery/planned_failover.md +++ b/doc/administration/geo/disaster_recovery/planned_failover.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The primary use-case of Disaster Recovery is to ensure business continuity in the event of unplanned outage, but it can be used in conjunction with a planned diff --git a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md index 77bd98e9834..1394ec2572a 100644 --- a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md +++ b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md @@ -12,7 +12,7 @@ This runbook is an [Experiment](../../../../policy/experiment-beta-support.md#ex DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Geo planned failover for a multi-node configuration diff --git a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md index 070377adbc9..96ab4a44a33 100644 --- a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md +++ b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md @@ -12,7 +12,7 @@ This runbook is an [Experiment](../../../../policy/experiment-beta-support.md#ex DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Geo planned failover for a single-node configuration diff --git a/doc/administration/geo/glossary.md b/doc/administration/geo/glossary.md index 8593a3c6669..39e8f9e5919 100644 --- a/doc/administration/geo/glossary.md +++ b/doc/administration/geo/glossary.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: We are updating the Geo documentation, user interface and commands to reflect these changes. Not all pages comply with diff --git a/doc/administration/geo/index.md b/doc/administration/geo/index.md index 9562fa110b8..74e4313e43f 100644 --- a/doc/administration/geo/index.md +++ b/doc/administration/geo/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Geo is the solution for widely distributed development teams and for providing a warm-standby as part of a disaster recovery strategy. diff --git a/doc/administration/geo/replication/configuration.md b/doc/administration/geo/replication/configuration.md index 07422201b74..eb2e0bbcde8 100644 --- a/doc/administration/geo/replication/configuration.md +++ b/doc/administration/geo/replication/configuration.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Configuring a new **secondary** site diff --git a/doc/administration/geo/replication/container_registry.md b/doc/administration/geo/replication/container_registry.md index fb2495b60fe..7a307372943 100644 --- a/doc/administration/geo/replication/container_registry.md +++ b/doc/administration/geo/replication/container_registry.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can set up a container registry on your **secondary** Geo site that mirrors the one on the **primary** Geo site. diff --git a/doc/administration/geo/replication/datatypes.md b/doc/administration/geo/replication/datatypes.md index de898d7b718..9f35a431c99 100644 --- a/doc/administration/geo/replication/datatypes.md +++ b/doc/administration/geo/replication/datatypes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed A Geo data type is a specific class of data that is required by one or more GitLab features to store relevant information. diff --git a/doc/administration/geo/replication/disable_geo.md b/doc/administration/geo/replication/disable_geo.md index 05ff39e9532..e8e9b588a7b 100644 --- a/doc/administration/geo/replication/disable_geo.md +++ b/doc/administration/geo/replication/disable_geo.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you want to revert to a regular Linux package installation setup after a test, or you have encountered a Disaster Recovery situation and you want to disable Geo momentarily, you can use these instructions to disable your diff --git a/doc/administration/geo/replication/faq.md b/doc/administration/geo/replication/faq.md index d5fadfecd12..0c5d78d6f98 100644 --- a/doc/administration/geo/replication/faq.md +++ b/doc/administration/geo/replication/faq.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## What are the minimum requirements to run Geo? diff --git a/doc/administration/geo/replication/geo_validation_tests.md b/doc/administration/geo/replication/geo_validation_tests.md index 4eaf81cb725..9f0aaebc8fe 100644 --- a/doc/administration/geo/replication/geo_validation_tests.md +++ b/doc/administration/geo/replication/geo_validation_tests.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Geo team performs manual testing and validation on common deployment configurations to ensure that Geo works when upgrading between minor GitLab versions and major PostgreSQL database versions. diff --git a/doc/administration/geo/replication/location_aware_git_url.md b/doc/administration/geo/replication/location_aware_git_url.md index 4c0e9ddbdf5..65df56d315e 100644 --- a/doc/administration/geo/replication/location_aware_git_url.md +++ b/doc/administration/geo/replication/location_aware_git_url.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: Since GitLab 14.6, diff --git a/doc/administration/geo/replication/multiple_servers.md b/doc/administration/geo/replication/multiple_servers.md index ca94b51e39a..0ea971074df 100644 --- a/doc/administration/geo/replication/multiple_servers.md +++ b/doc/administration/geo/replication/multiple_servers.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document describes a minimal reference architecture for running Geo in a multi-node configuration. If your multi-node setup differs from the one diff --git a/doc/administration/geo/replication/object_storage.md b/doc/administration/geo/replication/object_storage.md index da86bf3b2db..c35fab22695 100644 --- a/doc/administration/geo/replication/object_storage.md +++ b/doc/administration/geo/replication/object_storage.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > Verification of files stored in object storage was [introduced](https://gitlab.com/groups/gitlab-org/-/epics/8056) in GitLab 16.4 [with a flag](../../feature_flags.md) named `geo_object_storage_verification`. Enabled by default. diff --git a/doc/administration/geo/replication/remove_geo_site.md b/doc/administration/geo/replication/remove_geo_site.md index a3b893a77fe..d6bd634412d 100644 --- a/doc/administration/geo/replication/remove_geo_site.md +++ b/doc/administration/geo/replication/remove_geo_site.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed **Secondary** sites can be removed from the Geo cluster using the Geo administration page of the **primary** site. To remove a **secondary** site: diff --git a/doc/administration/geo/replication/security_review.md b/doc/administration/geo/replication/security_review.md index 58d1d1278d3..95dd33ecc02 100644 --- a/doc/administration/geo/replication/security_review.md +++ b/doc/administration/geo/replication/security_review.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following security review of the Geo feature set focuses on security aspects of the feature as they apply to customers running their own GitLab instances. The review diff --git a/doc/administration/geo/replication/single_sign_on.md b/doc/administration/geo/replication/single_sign_on.md index 3b1b5e569a0..305cb4d8725 100644 --- a/doc/administration/geo/replication/single_sign_on.md +++ b/doc/administration/geo/replication/single_sign_on.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This documentation only discusses Geo-specific SSO considerations and configuration. For more information on general authentication, see [GitLab authentication and authorization](../../auth/index.md). diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index e3c1dee30b8..694aac49f08 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Setting up Geo requires careful attention to details, and sometimes it's easy to miss a step. diff --git a/doc/administration/geo/replication/tuning.md b/doc/administration/geo/replication/tuning.md index ace0c783f45..6f5491292b8 100644 --- a/doc/administration/geo/replication/tuning.md +++ b/doc/administration/geo/replication/tuning.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can limit the number of concurrent operations the sites can run in the background. diff --git a/doc/administration/geo/replication/upgrading_the_geo_sites.md b/doc/administration/geo/replication/upgrading_the_geo_sites.md index bac2c4b95f5..b9e9fac85ad 100644 --- a/doc/administration/geo/replication/upgrading_the_geo_sites.md +++ b/doc/administration/geo/replication/upgrading_the_geo_sites.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: Read these sections carefully before updating your Geo sites. Not following diff --git a/doc/administration/geo/replication/usage.md b/doc/administration/geo/replication/usage.md index 6d2904dc28a..4e62c87bf06 100644 --- a/doc/administration/geo/replication/usage.md +++ b/doc/administration/geo/replication/usage.md @@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed After you set up the [database replication and configure the Geo nodes](../index.md#setup-instructions), use your closest GitLab site as you would do with the primary one. diff --git a/doc/administration/geo/secondary_proxy/index.md b/doc/administration/geo/secondary_proxy/index.md index e908eab4ea5..61d6369c56c 100644 --- a/doc/administration/geo/secondary_proxy/index.md +++ b/doc/administration/geo/secondary_proxy/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/5914) in GitLab 14.4 [with a flag](../../feature_flags.md) named `geo_secondary_proxy`. Disabled by default. > - [Enabled by default for unified URLs](https://gitlab.com/gitlab-org/gitlab/-/issues/325732) in GitLab 14.6. diff --git a/doc/administration/geo/secondary_proxy/location_aware_external_url.md b/doc/administration/geo/secondary_proxy/location_aware_external_url.md index 570df5dd546..5865498210d 100644 --- a/doc/administration/geo/secondary_proxy/location_aware_external_url.md +++ b/doc/administration/geo/secondary_proxy/location_aware_external_url.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed With [Geo proxying for secondary sites](index.md), you can provide GitLab users with a single URL that automatically uses the Geo site closest to them. diff --git a/doc/administration/geo/secondary_proxy/runners.md b/doc/administration/geo/secondary_proxy/runners.md index 02752e753f7..e630c0921c9 100644 --- a/doc/administration/geo/secondary_proxy/runners.md +++ b/doc/administration/geo/secondary_proxy/runners.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed **Status:** Experiment > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/415179) in GitLab 16.7 [with a flag](../../feature_flags.md) named `geo_proxy_check_pipeline_refs`. Enabled by default in 16.9 diff --git a/doc/administration/geo/setup/database.md b/doc/administration/geo/setup/database.md index d56e2f4bde1..19c6e282666 100644 --- a/doc/administration/geo/setup/database.md +++ b/doc/administration/geo/setup/database.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document describes the minimal required steps to replicate your primary GitLab database to a secondary site's database. You may have to change some diff --git a/doc/administration/geo/setup/external_database.md b/doc/administration/geo/setup/external_database.md index e9b2f8fd6dc..08af4685ec1 100644 --- a/doc/administration/geo/setup/external_database.md +++ b/doc/administration/geo/setup/external_database.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document is relevant if you are using a PostgreSQL instance that is not managed by the Linux package. This includes diff --git a/doc/administration/geo/setup/index.md b/doc/administration/geo/setup/index.md index 17ca1085306..4b69ac4df93 100644 --- a/doc/administration/geo/setup/index.md +++ b/doc/administration/geo/setup/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Prerequisites diff --git a/doc/administration/geo/setup/two_single_node_external_services.md b/doc/administration/geo/setup/two_single_node_external_services.md index 6d323399de7..fdc5acd5f97 100644 --- a/doc/administration/geo/setup/two_single_node_external_services.md +++ b/doc/administration/geo/setup/two_single_node_external_services.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following guide provides concise instructions on how to deploy GitLab Geo for a two single-node site installation using two Linux package instances and external PostgreSQL databases like RDS, Azure Database, or Google Cloud SQL. diff --git a/doc/administration/geo/setup/two_single_node_sites.md b/doc/administration/geo/setup/two_single_node_sites.md index 38752d9e9ed..f1b2594ea55 100644 --- a/doc/administration/geo/setup/two_single_node_sites.md +++ b/doc/administration/geo/setup/two_single_node_sites.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following guide provides concise instructions on how to deploy GitLab Geo for a two single-node site installation using two Linux package instances with no external services set up. diff --git a/doc/administration/geo_sites.md b/doc/administration/geo_sites.md index 19e1a6368ff..efdba56d253 100644 --- a/doc/administration/geo_sites.md +++ b/doc/administration/geo_sites.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can configure various settings for GitLab Geo sites. For more information, see [Geo documentation](../administration/geo/index.md). diff --git a/doc/administration/get_started.md b/doc/administration/get_started.md index 16e6c6b5ab6..fa2d76c2de1 100644 --- a/doc/administration/get_started.md +++ b/doc/administration/get_started.md @@ -9,7 +9,7 @@ info: For assistance with this tutorial, see https://handbook.gitlab.com/handboo DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Get started with GitLab administration. Configure your organization and its authentication, then secure, monitor, and back up GitLab. @@ -189,7 +189,7 @@ It is common for a VM snapshot to require you to power down the server. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Geo provides local, read-only instances of your GitLab instances. diff --git a/doc/administration/git_protocol.md b/doc/administration/git_protocol.md index 43730ff3878..a2f88b08503 100644 --- a/doc/administration/git_protocol.md +++ b/doc/administration/git_protocol.md @@ -9,7 +9,7 @@ description: "Set and configure Git protocol v2" DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Re-enabled](https://gitlab.com/gitlab-org/gitlab/-/issues/27828) in GitLab 12.8. diff --git a/doc/administration/gitaly/configure_gitaly.md b/doc/administration/gitaly/configure_gitaly.md index 6e3e369f6ce..861e0eea3ed 100644 --- a/doc/administration/gitaly/configure_gitaly.md +++ b/doc/administration/gitaly/configure_gitaly.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Configure Gitaly in one of two ways: @@ -886,7 +886,7 @@ result as you did at the start. For example: DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed [Gitaly](index.md), the service that provides storage for Git repositories, can be configured to cache a short rolling window of Git @@ -1130,7 +1130,7 @@ Configure the `cat-file` cache in the [Gitaly configuration file](reference.md). FLAG: On self-managed GitLab, by default this feature is not available. To make it available, an administrator can [enable the feature flag](../feature_flags.md) named `gitaly_gpg_signing`. -On GitLab.com, this feature is available. +On GitLab.com, this feature is not available. By default, Gitaly doesn't sign commits made using GitLab UI. For example, commits made using: diff --git a/doc/administration/gitaly/index.md b/doc/administration/gitaly/index.md index 312974ca423..2f096f5283e 100644 --- a/doc/administration/gitaly/index.md +++ b/doc/administration/gitaly/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed [Gitaly](https://gitlab.com/gitlab-org/gitaly) provides high-level RPC access to Git repositories. It is used by GitLab to read and write Git data. diff --git a/doc/administration/gitaly/praefect.md b/doc/administration/gitaly/praefect.md index c3d44c7b44b..66a4224ec65 100644 --- a/doc/administration/gitaly/praefect.md +++ b/doc/administration/gitaly/praefect.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Configure Gitaly Cluster using either: diff --git a/doc/administration/gitaly/reference.md b/doc/administration/gitaly/reference.md index adfe02ee270..0a2943fff35 100644 --- a/doc/administration/gitaly/reference.md +++ b/doc/administration/gitaly/reference.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Gitaly and Gitaly Cluster are configured by using configuration files. The default location of the configuration files depends on the type of installation you have: diff --git a/doc/administration/gitaly/troubleshooting.md b/doc/administration/gitaly/troubleshooting.md index f4e03033112..e0f574f720f 100644 --- a/doc/administration/gitaly/troubleshooting.md +++ b/doc/administration/gitaly/troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Refer to the information below when troubleshooting Gitaly. For information on troubleshooting Gitaly Cluster (Praefect), see [Troubleshooting Gitaly Cluster](troubleshooting_gitaly_cluster.md). diff --git a/doc/administration/gitaly/troubleshooting_gitaly_cluster.md b/doc/administration/gitaly/troubleshooting_gitaly_cluster.md index 0755d7e6b8a..1f0b75602bb 100644 --- a/doc/administration/gitaly/troubleshooting_gitaly_cluster.md +++ b/doc/administration/gitaly/troubleshooting_gitaly_cluster.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Refer to the information below when troubleshooting Gitaly Cluster (Praefect). For information on troubleshooting Gitaly, see [Troubleshooting Gitaly](troubleshooting.md). diff --git a/doc/administration/inactive_project_deletion.md b/doc/administration/inactive_project_deletion.md index 757279b66b9..53a018d243f 100644 --- a/doc/administration/inactive_project_deletion.md +++ b/doc/administration/inactive_project_deletion.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/85689) in GitLab 15.0 [with a flag](../administration/feature_flags.md) named `inactive_projects_deletion`. Disabled by default. > - [Feature flag `inactive_projects_deletion`](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96803) removed in GitLab 15.4. diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md index 2c00a846a83..0d8bd737bd5 100644 --- a/doc/administration/instance_limits.md +++ b/doc/administration/instance_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab, like most large applications, enforces limits in certain features to maintain a minimum quality of performance. Allowing some features to be limitless could affect security, diff --git a/doc/administration/instance_review.md b/doc/administration/instance_review.md index 525efa3b665..cd67ee34a12 100644 --- a/doc/administration/instance_review.md +++ b/doc/administration/instance_review.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you run a self-managed instance with 50 or more users on the Free tier ([either Community Edition or unlicensed Enterprise Edition](https://about.gitlab.com/install/ce-or-ee/)), diff --git a/doc/administration/integration/diagrams_net.md b/doc/administration/integration/diagrams_net.md index b4424d36c57..9fb9e3eb1d1 100644 --- a/doc/administration/integration/diagrams_net.md +++ b/doc/administration/integration/diagrams_net.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/86206) in GitLab 15.10. > - Offline environment support [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/116281) in GitLab 16.1. diff --git a/doc/administration/integration/kroki.md b/doc/administration/integration/kroki.md index 0659db3a014..bbd1027e802 100644 --- a/doc/administration/integration/kroki.md +++ b/doc/administration/integration/kroki.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241744) in GitLab 13.7. > - Support for reStructuredText and Textile documents [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/324766) in GitLab 13.12. diff --git a/doc/administration/integration/mailgun.md b/doc/administration/integration/mailgun.md index 8bf279c3299..35ece000dc2 100644 --- a/doc/administration/integration/mailgun.md +++ b/doc/administration/integration/mailgun.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed When you use Mailgun to send emails for your GitLab instance and [Mailgun](https://www.mailgun.com/) integration is enabled and configured in GitLab, you can receive their webhook for diff --git a/doc/administration/integration/plantuml.md b/doc/administration/integration/plantuml.md index 782c43991db..f6e4cedd1ee 100644 --- a/doc/administration/integration/plantuml.md +++ b/doc/administration/integration/plantuml.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed With the [PlantUML](https://plantuml.com) integration, you can create diagrams in snippets, wikis, and repositories. This integration is enabled on GitLab.com for all SaaS users and does not require any additional configuration. diff --git a/doc/administration/integration/terminal.md b/doc/administration/integration/terminal.md index e0b31b56a10..bd0b589f9b8 100644 --- a/doc/administration/integration/terminal.md +++ b/doc/administration/integration/terminal.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Deprecated](https://gitlab.com/groups/gitlab-org/configure/-/epics/8) in GitLab 14.5. > - [Disabled on self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/353410) in GitLab 15.0. diff --git a/doc/administration/invalidate_markdown_cache.md b/doc/administration/invalidate_markdown_cache.md index d167c5893e5..4832bfec198 100644 --- a/doc/administration/invalidate_markdown_cache.md +++ b/doc/administration/invalidate_markdown_cache.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed For performance reasons, GitLab caches the HTML version of Markdown text in fields such as: diff --git a/doc/administration/issue_closing_pattern.md b/doc/administration/issue_closing_pattern.md index b37fbd8af2e..16d50c79313 100644 --- a/doc/administration/issue_closing_pattern.md +++ b/doc/administration/issue_closing_pattern.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: This page explains how an administrator can configure issue closing patterns. diff --git a/doc/administration/job_artifacts.md b/doc/administration/job_artifacts.md index eda7cf0b1c7..689b18c676e 100644 --- a/doc/administration/job_artifacts.md +++ b/doc/administration/job_artifacts.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This is the administration documentation. To learn how to use job artifacts in your GitLab CI/CD pipeline, see the [job artifacts configuration documentation](../ci/jobs/job_artifacts.md). diff --git a/doc/administration/job_logs.md b/doc/administration/job_logs.md index 622db1c1e98..8fe09c8405e 100644 --- a/doc/administration/job_logs.md +++ b/doc/administration/job_logs.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Job logs are sent by a runner while it's processing a job. You can see logs in job pages, pipelines, email notifications, and so on. diff --git a/doc/administration/labels.md b/doc/administration/labels.md index be5ad9a203b..66bd59b8f3b 100644 --- a/doc/administration/labels.md +++ b/doc/administration/labels.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To manage labels for the GitLab instance: diff --git a/doc/administration/lfs/index.md b/doc/administration/lfs/index.md index 70307c2fb45..64fffd572fd 100644 --- a/doc/administration/lfs/index.md +++ b/doc/administration/lfs/index.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains information about configuring Git LFS in self-managed GitLab instances. For user documentation about Git LFS, see [Git Large File Storage](../../topics/git/lfs/index.md). diff --git a/doc/administration/libravatar.md b/doc/administration/libravatar.md index 2ebc6b1912e..5d72e655bd5 100644 --- a/doc/administration/libravatar.md +++ b/doc/administration/libravatar.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab by default supports the [Gravatar](https://gravatar.com) avatar service. diff --git a/doc/administration/license.md b/doc/administration/license.md index 0ea6ac5c7ad..53d44bf6dbf 100644 --- a/doc/administration/license.md +++ b/doc/administration/license.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed When you install a new GitLab instance without a license, only Free features are enabled. To enable more features in GitLab Enterprise Edition (EE), activate diff --git a/doc/administration/load_balancer.md b/doc/administration/load_balancer.md index 13c6724b533..c941734e5ff 100644 --- a/doc/administration/load_balancer.md +++ b/doc/administration/load_balancer.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed In a multi-node GitLab configuration, you need a load balancer to route traffic to the application servers. The specifics on which load balancer to use diff --git a/doc/administration/logs/index.md b/doc/administration/logs/index.md index b06a8896873..ff55229c296 100644 --- a/doc/administration/logs/index.md +++ b/doc/administration/logs/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab has an advanced log system where everything is logged, so you can analyze your instance using various system log files. The log system is similar to [audit events](../audit_events.md). @@ -896,7 +896,7 @@ are generated in a location based on your installation method: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/15442) in GitLab 12.3. @@ -910,7 +910,7 @@ This file is located at: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/110980) in GitLab 15.9. @@ -927,7 +927,7 @@ This file is located at: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - Introduced in GitLab 12.6. @@ -1007,7 +1007,7 @@ For example: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Geo stores structured log messages in a `geo.log` file. For Linux package installations, this file is at `/var/log/gitlab/gitlab-rails/geo.log`. diff --git a/doc/administration/logs/log_parsing.md b/doc/administration/logs/log_parsing.md index 839f54aa74c..b884f25877e 100644 --- a/doc/administration/logs/log_parsing.md +++ b/doc/administration/logs/log_parsing.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed We recommend using log aggregation and search tools like Kibana and Splunk whenever possible, but if they are not available you can still quickly parse diff --git a/doc/administration/logs/tracing_correlation_id.md b/doc/administration/logs/tracing_correlation_id.md index 722c1d99613..33e37f3f1b9 100644 --- a/doc/administration/logs/tracing_correlation_id.md +++ b/doc/administration/logs/tracing_correlation_id.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab instances log a unique request tracking ID (known as the "correlation ID") for most requests. Each individual request to GitLab gets diff --git a/doc/administration/maintenance_mode/index.md b/doc/administration/maintenance_mode/index.md index b5848bea91c..31afe3a6a40 100644 --- a/doc/administration/maintenance_mode/index.md +++ b/doc/administration/maintenance_mode/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2149) in GitLab 13.9. diff --git a/doc/administration/merge_request_diffs.md b/doc/administration/merge_request_diffs.md index e871ba3fa21..51297916efb 100644 --- a/doc/administration/merge_request_diffs.md +++ b/doc/administration/merge_request_diffs.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Merge request diffs are size-limited copies of diffs associated with merge requests. When viewing a merge request, diffs are sourced from these copies diff --git a/doc/administration/merge_requests_approvals.md b/doc/administration/merge_requests_approvals.md index 55775e4be99..4035f472924 100644 --- a/doc/administration/merge_requests_approvals.md +++ b/doc/administration/merge_requests_approvals.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/39060) in GitLab 12.8. diff --git a/doc/administration/moderate_users.md b/doc/administration/moderate_users.md index a2ff1b3a818..76fdbe958e3 100644 --- a/doc/administration/moderate_users.md +++ b/doc/administration/moderate_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This is the administration documentation. For information about moderating users at the group level, see the [group-level documentation](../user/group/moderate_users.md). @@ -192,7 +192,7 @@ GitLab generated bots are excluded from the automatic deactivation of dormant us DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352514) in GitLab 16.1 [with a flag](../administration/feature_flags.md) named `delete_unconfirmed_users_setting`. Disabled by default. > - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124982) in GitLab 16.2. diff --git a/doc/administration/monitoring/github_imports.md b/doc/administration/monitoring/github_imports.md index 49086fc1b70..d4c075db6c3 100644 --- a/doc/administration/monitoring/github_imports.md +++ b/doc/administration/monitoring/github_imports.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The GitHub importer exposes various Prometheus metrics that you can use to monitor the health and progress of the importer. diff --git a/doc/administration/monitoring/health_check.md b/doc/administration/monitoring/health_check.md index 28ecc1f514d..665d9b86191 100644 --- a/doc/administration/monitoring/health_check.md +++ b/doc/administration/monitoring/health_check.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab provides liveness and readiness probes to indicate service health and reachability to required services. These probes report on the status of the diff --git a/doc/administration/monitoring/index.md b/doc/administration/monitoring/index.md index 2e78f05a138..d58e63eb04f 100644 --- a/doc/administration/monitoring/index.md +++ b/doc/administration/monitoring/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Explore our features to monitor your GitLab instance: diff --git a/doc/administration/monitoring/ip_allowlist.md b/doc/administration/monitoring/ip_allowlist.md index ef39446c3c0..ab59b8e525c 100644 --- a/doc/administration/monitoring/ip_allowlist.md +++ b/doc/administration/monitoring/ip_allowlist.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab provides some [monitoring endpoints](health_check.md) that provide health check information when probed. diff --git a/doc/administration/monitoring/performance/gitlab_configuration.md b/doc/administration/monitoring/performance/gitlab_configuration.md index de8e03cba0f..458d586c803 100644 --- a/doc/administration/monitoring/performance/gitlab_configuration.md +++ b/doc/administration/monitoring/performance/gitlab_configuration.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab Performance Monitoring is disabled by default. To enable it and change any of its settings: diff --git a/doc/administration/monitoring/performance/grafana_configuration.md b/doc/administration/monitoring/performance/grafana_configuration.md index f7c55225b2a..e353e03f557 100644 --- a/doc/administration/monitoring/performance/grafana_configuration.md +++ b/doc/administration/monitoring/performance/grafana_configuration.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - Grafana bundled with GitLab was [deprecated](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7772) in GitLab 16.0. > - Grafana bundled with GitLab was [removed](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7772) in GitLab 16.3. diff --git a/doc/administration/monitoring/performance/index.md b/doc/administration/monitoring/performance/index.md index 2734802c4b4..18ef0031cb8 100644 --- a/doc/administration/monitoring/performance/index.md +++ b/doc/administration/monitoring/performance/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab comes with its own application performance measuring system as of GitLab 8.4, called "GitLab Performance Monitoring". GitLab Performance Monitoring is available in both the diff --git a/doc/administration/monitoring/performance/performance_bar.md b/doc/administration/monitoring/performance/performance_bar.md index 44b02858dbc..e9a209f7d39 100644 --- a/doc/administration/monitoring/performance/performance_bar.md +++ b/doc/administration/monitoring/performance/performance_bar.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - The **Stats** field [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/271551) in GitLab 13.9. > - The **Memory** field [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/330736) in GitLab 14.0. diff --git a/doc/administration/monitoring/prometheus/gitlab_exporter.md b/doc/administration/monitoring/prometheus/gitlab_exporter.md index cb3c3930ae6..f57144a799f 100644 --- a/doc/administration/monitoring/prometheus/gitlab_exporter.md +++ b/doc/administration/monitoring/prometheus/gitlab_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > Renamed from `GitLab monitor exporter` to `GitLab exporter` in [GitLab 12.3](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16511). diff --git a/doc/administration/monitoring/prometheus/gitlab_metrics.md b/doc/administration/monitoring/prometheus/gitlab_metrics.md index efdde981ea9..9e2a03b3ed9 100644 --- a/doc/administration/monitoring/prometheus/gitlab_metrics.md +++ b/doc/administration/monitoring/prometheus/gitlab_metrics.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To enable the GitLab Prometheus metrics: @@ -418,7 +418,7 @@ configuration option in `gitlab.yml`. These metrics are served from the DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following metrics are available: @@ -432,7 +432,7 @@ The following metrics are available: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The following metrics are available: diff --git a/doc/administration/monitoring/prometheus/index.md b/doc/administration/monitoring/prometheus/index.md index 4fb4d8d0dcb..1bddbbc25c2 100644 --- a/doc/administration/monitoring/prometheus/index.md +++ b/doc/administration/monitoring/prometheus/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed [Prometheus](https://prometheus.io) is a powerful time-series monitoring service, providing a flexible platform for monitoring GitLab and other software products. diff --git a/doc/administration/monitoring/prometheus/node_exporter.md b/doc/administration/monitoring/prometheus/node_exporter.md index cbd8687da39..6acb3737bc7 100644 --- a/doc/administration/monitoring/prometheus/node_exporter.md +++ b/doc/administration/monitoring/prometheus/node_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The [node exporter](https://github.com/prometheus/node_exporter) enables you to measure various machine resources such as memory, disk and CPU utilization. diff --git a/doc/administration/monitoring/prometheus/pgbouncer_exporter.md b/doc/administration/monitoring/prometheus/pgbouncer_exporter.md index 9f985e6f907..26f85f7173d 100644 --- a/doc/administration/monitoring/prometheus/pgbouncer_exporter.md +++ b/doc/administration/monitoring/prometheus/pgbouncer_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The [PgBouncer exporter](https://github.com/prometheus-community/pgbouncer_exporter) enables you to measure various [PgBouncer](https://www.pgbouncer.org/) metrics. diff --git a/doc/administration/monitoring/prometheus/postgres_exporter.md b/doc/administration/monitoring/prometheus/postgres_exporter.md index faa92146095..a10c06ff8a9 100644 --- a/doc/administration/monitoring/prometheus/postgres_exporter.md +++ b/doc/administration/monitoring/prometheus/postgres_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The [PostgreSQL Server Exporter](https://github.com/prometheus-community/postgres_exporter) allows you to export various PostgreSQL metrics. diff --git a/doc/administration/monitoring/prometheus/redis_exporter.md b/doc/administration/monitoring/prometheus/redis_exporter.md index a849271f862..dabcaa629af 100644 --- a/doc/administration/monitoring/prometheus/redis_exporter.md +++ b/doc/administration/monitoring/prometheus/redis_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The [Redis exporter](https://github.com/oliver006/redis_exporter) enables you to measure various [Redis](https://redis.io) metrics. For more information on what is exported, diff --git a/doc/administration/monitoring/prometheus/registry_exporter.md b/doc/administration/monitoring/prometheus/registry_exporter.md index 842c38d7802..70624e76de2 100644 --- a/doc/administration/monitoring/prometheus/registry_exporter.md +++ b/doc/administration/monitoring/prometheus/registry_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Registry exporter allows you to measure various Registry metrics. To enable it: diff --git a/doc/administration/monitoring/prometheus/web_exporter.md b/doc/administration/monitoring/prometheus/web_exporter.md index 8f2619713c9..7cb4e8ceefe 100644 --- a/doc/administration/monitoring/prometheus/web_exporter.md +++ b/doc/administration/monitoring/prometheus/web_exporter.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed When [monitoring GitLab with Prometheus](index.md), GitLab runs various collectors that sample the application for data related to usage, load and performance. GitLab can then make diff --git a/doc/administration/nfs.md b/doc/administration/nfs.md index 1019656fc51..4a669f84d60 100644 --- a/doc/administration/nfs.md +++ b/doc/administration/nfs.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NFS can be used as an alternative for object storage but this isn't typically recommended for performance reasons. diff --git a/doc/administration/object_storage.md b/doc/administration/object_storage.md index b1b96c9a72d..cfe573a1b76 100644 --- a/doc/administration/object_storage.md +++ b/doc/administration/object_storage.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab supports using an object storage service for holding numerous types of data. It's recommended over NFS and diff --git a/doc/administration/operations/fast_ssh_key_lookup.md b/doc/administration/operations/fast_ssh_key_lookup.md index 6be35092535..e2e36268195 100644 --- a/doc/administration/operations/fast_ssh_key_lookup.md +++ b/doc/administration/operations/fast_ssh_key_lookup.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: This document describes a drop-in replacement for the diff --git a/doc/administration/operations/filesystem_benchmarking.md b/doc/administration/operations/filesystem_benchmarking.md index 2a595791fff..16f20efe3c1 100644 --- a/doc/administration/operations/filesystem_benchmarking.md +++ b/doc/administration/operations/filesystem_benchmarking.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed File system performance has a big impact on overall GitLab performance, especially for actions that read or write to Git repositories. This information diff --git a/doc/administration/operations/gitlab_sshd.md b/doc/administration/operations/gitlab_sshd.md index bcd293b00fa..7ba4d20aa7c 100644 --- a/doc/administration/operations/gitlab_sshd.md +++ b/doc/administration/operations/gitlab_sshd.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/299109) in GitLab 14.5 as an Experiment for self-managed customers. > - Ready for production use with [Cloud Native GitLab in GitLab 15.1](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2540) and [Linux packages in GitLab 15.9](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5937). diff --git a/doc/administration/operations/index.md b/doc/administration/operations/index.md index aa782dcbe89..145263374bf 100644 --- a/doc/administration/operations/index.md +++ b/doc/administration/operations/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Keep your GitLab instance up and running. diff --git a/doc/administration/operations/moving_repositories.md b/doc/administration/operations/moving_repositories.md index 184f53014fd..a38f4301ce5 100644 --- a/doc/administration/operations/moving_repositories.md +++ b/doc/administration/operations/moving_repositories.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can move all repositories managed by GitLab to another file system or another server. @@ -142,7 +142,7 @@ To move all snippets by using the API: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To move all groups by using the API: diff --git a/doc/administration/operations/puma.md b/doc/administration/operations/puma.md index ccdaf1e1c77..0b353981fb4 100644 --- a/doc/administration/operations/puma.md +++ b/doc/administration/operations/puma.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Puma is a fast, multi-threaded, and highly concurrent HTTP 1.1 server for Ruby applications. It runs the core Rails application that provides the user-facing diff --git a/doc/administration/operations/rails_console.md b/doc/administration/operations/rails_console.md index 925f53660c7..05a59433762 100644 --- a/doc/administration/operations/rails_console.md +++ b/doc/administration/operations/rails_console.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed At the heart of GitLab is a web application [built using the Ruby on Rails framework](https://about.gitlab.com/blog/2018/10/29/why-we-use-rails-to-build-gitlab/). diff --git a/doc/administration/operations/ssh_certificates.md b/doc/administration/operations/ssh_certificates.md index 0745b219339..ddc64153d9d 100644 --- a/doc/administration/operations/ssh_certificates.md +++ b/doc/administration/operations/ssh_certificates.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/19911) in GitLab 11.2. diff --git a/doc/administration/package_information/defaults.md b/doc/administration/package_information/defaults.md index 6aa9b1b54cb..d8d0cb1a9d7 100644 --- a/doc/administration/package_information/defaults.md +++ b/doc/administration/package_information/defaults.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Unless configuration is specified in the `/etc/gitlab/gitlab.rb` file, the package assumes the defaults as noted below. diff --git a/doc/administration/package_information/deprecation_policy.md b/doc/administration/package_information/deprecation_policy.md index 1eccee48cf9..15d0b78e992 100644 --- a/doc/administration/package_information/deprecation_policy.md +++ b/doc/administration/package_information/deprecation_policy.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Linux packages come with number of different libraries and services which offers users plethora of configuration options. diff --git a/doc/administration/package_information/index.md b/doc/administration/package_information/index.md index ea5863dddce..cae621ebd5b 100644 --- a/doc/administration/package_information/index.md +++ b/doc/administration/package_information/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Linux package is bundled with all dependencies required for GitLab to function correctly. More details can be found diff --git a/doc/administration/package_information/licensing.md b/doc/administration/package_information/licensing.md index 319ee74b0b1..85dbf743f47 100644 --- a/doc/administration/package_information/licensing.md +++ b/doc/administration/package_information/licensing.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## License diff --git a/doc/administration/package_information/omnibus_packages.md b/doc/administration/package_information/omnibus_packages.md index d219eab3363..a026d6c16a7 100644 --- a/doc/administration/package_information/omnibus_packages.md +++ b/doc/administration/package_information/omnibus_packages.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Below you can find some basic information on why GitLab provides packages and a Docker image that come with bundled dependencies. diff --git a/doc/administration/package_information/postgresql_versions.md b/doc/administration/package_information/postgresql_versions.md index 2cc0d4244c0..7036e7eb0e8 100644 --- a/doc/administration/package_information/postgresql_versions.md +++ b/doc/administration/package_information/postgresql_versions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: This table lists only GitLab versions where a significant change happened in the diff --git a/doc/administration/package_information/signed_packages.md b/doc/administration/package_information/signed_packages.md index 41918006c1f..a2fbcc8362d 100644 --- a/doc/administration/package_information/signed_packages.md +++ b/doc/administration/package_information/signed_packages.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Linux packages produced by GitLab are created using [Omnibus](https://github.com/chef/omnibus), for which GitLab has added DEB signing using `debsigs` in [our own fork](https://gitlab.com/gitlab-org/omnibus). diff --git a/doc/administration/package_information/supported_os.md b/doc/administration/package_information/supported_os.md index 92e619306be..600e9b8f8ea 100644 --- a/doc/administration/package_information/supported_os.md +++ b/doc/administration/package_information/supported_os.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab officially supports LTS versions of operating systems. While OSs like Ubuntu have a clear distinction between LTS and non-LTS versions, there are diff --git a/doc/administration/packages/container_registry.md b/doc/administration/packages/container_registry.md index b08850f68e8..116c851de1d 100644 --- a/doc/administration/packages/container_registry.md +++ b/doc/administration/packages/container_registry.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: The [next-generation container registry](container_registry_metadata_database.md) @@ -1099,7 +1099,7 @@ end DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed **Status:** Beta The metadata database enables many new registry features, including diff --git a/doc/administration/packages/container_registry_metadata_database.md b/doc/administration/packages/container_registry_metadata_database.md index c46b11c399a..2cbc457abca 100644 --- a/doc/administration/packages/container_registry_metadata_database.md +++ b/doc/administration/packages/container_registry_metadata_database.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed **Status:** Beta > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/423459) in GitLab 16.4 as a [Beta feature](../../policy/experiment-beta-support.md) for self-managed GitLab instances. diff --git a/doc/administration/packages/dependency_proxy.md b/doc/administration/packages/dependency_proxy.md index ed73a2eac62..44e343fc113 100644 --- a/doc/administration/packages/dependency_proxy.md +++ b/doc/administration/packages/dependency_proxy.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7934) in [GitLab Premium](https://about.gitlab.com/pricing/) 11.11. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/273655) from GitLab Premium to GitLab Free in 13.6. diff --git a/doc/administration/packages/index.md b/doc/administration/packages/index.md index 3246f9bd45e..136a45cb09d 100644 --- a/doc/administration/packages/index.md +++ b/doc/administration/packages/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To use GitLab as a private repository for a variety of common package managers, use the package registry. You can build and publish diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md index 99c9efe09a0..a9f57fdbf03 100644 --- a/doc/administration/pages/index.md +++ b/doc/administration/pages/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab Pages allows for hosting of static sites. It must be configured by an administrator. Separate [user documentation](../../user/project/pages/index.md) is available. @@ -836,7 +836,7 @@ Follow the steps below to configure the proxy listener of GitLab Pages. DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Prerequisites: @@ -854,7 +854,7 @@ To set the global maximum pages size for a project: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Prerequisites: @@ -872,7 +872,7 @@ To set the maximum size of each GitLab Pages site in a group, overriding the inh DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Prerequisites: diff --git a/doc/administration/pages/source.md b/doc/administration/pages/source.md index d8a80d22486..e33d1a47a8a 100644 --- a/doc/administration/pages/source.md +++ b/doc/administration/pages/source.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: Before attempting to enable GitLab Pages, first make sure you have diff --git a/doc/administration/pages/troubleshooting.md b/doc/administration/pages/troubleshooting.md index 8d942a55ea3..60bf8af4fa0 100644 --- a/doc/administration/pages/troubleshooting.md +++ b/doc/administration/pages/troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains a list of issues you might encounter when administering GitLab Pages. diff --git a/doc/administration/polling.md b/doc/administration/polling.md index a4b63045a5b..3826ca29067 100644 --- a/doc/administration/polling.md +++ b/doc/administration/polling.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The GitLab UI polls for updates for different resources (such as issue notes, issue titles, and pipeline statuses) on a schedule appropriate to the resource. diff --git a/doc/administration/postgresql/database_load_balancing.md b/doc/administration/postgresql/database_load_balancing.md index 7dff9149682..b879d19b622 100644 --- a/doc/administration/postgresql/database_load_balancing.md +++ b/doc/administration/postgresql/database_load_balancing.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/1283) in [GitLab Premium](https://about.gitlab.com/pricing/) 9.0. > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60894) from GitLab Premium to GitLab Free in 14.0. diff --git a/doc/administration/postgresql/external.md b/doc/administration/postgresql/external.md index 22521f8f611..ff6ba1c6f5f 100644 --- a/doc/administration/postgresql/external.md +++ b/doc/administration/postgresql/external.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you're hosting GitLab on a cloud provider, you can optionally use a managed service for PostgreSQL. For example, AWS offers a managed Relational diff --git a/doc/administration/postgresql/index.md b/doc/administration/postgresql/index.md index cb926c2300e..f913579e941 100644 --- a/doc/administration/postgresql/index.md +++ b/doc/administration/postgresql/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed In this section, you are guided through configuring a PostgreSQL database to be used with GitLab in one of our [reference architectures](../reference_architectures/index.md). @@ -42,7 +42,7 @@ Read more about [monitoring and logging setup for external Databases](external_m DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This setup is for when you have installed GitLab using the [Linux **Enterprise Edition** (EE) package](https://about.gitlab.com/install/?version=ee). diff --git a/doc/administration/postgresql/moving.md b/doc/administration/postgresql/moving.md index 509a6f91d71..21184480541 100644 --- a/doc/administration/postgresql/moving.md +++ b/doc/administration/postgresql/moving.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Sometimes it is necessary to move your databases from one PostgreSQL instance to another. For example, if you are using AWS Aurora and are preparing to diff --git a/doc/administration/postgresql/multiple_databases.md b/doc/administration/postgresql/multiple_databases.md index ea43850f271..f7990a16031 100644 --- a/doc/administration/postgresql/multiple_databases.md +++ b/doc/administration/postgresql/multiple_databases.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/6168) in GitLab 15.7. diff --git a/doc/administration/postgresql/pgbouncer.md b/doc/administration/postgresql/pgbouncer.md index aba0f947146..78b14b77ecf 100644 --- a/doc/administration/postgresql/pgbouncer.md +++ b/doc/administration/postgresql/pgbouncer.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: PgBouncer is bundled in the `gitlab-ee` package, but is free to use. diff --git a/doc/administration/postgresql/replication_and_failover.md b/doc/administration/postgresql/replication_and_failover.md index 2191c59f3ec..5810103eb7f 100644 --- a/doc/administration/postgresql/replication_and_failover.md +++ b/doc/administration/postgresql/replication_and_failover.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you're a Free user of GitLab self-managed, consider using a cloud-hosted solution. This document doesn't cover self-compiled installations. diff --git a/doc/administration/postgresql/replication_and_failover_troubleshooting.md b/doc/administration/postgresql/replication_and_failover_troubleshooting.md index 42bb5ac525c..7a4e70e0809 100644 --- a/doc/administration/postgresql/replication_and_failover_troubleshooting.md +++ b/doc/administration/postgresql/replication_and_failover_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed When working with PostgreSQL replication and failover, you might encounter the following issues. diff --git a/doc/administration/postgresql/standalone.md b/doc/administration/postgresql/standalone.md index cbbbe63a227..b1404a91928 100644 --- a/doc/administration/postgresql/standalone.md +++ b/doc/administration/postgresql/standalone.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you wish to have your database service hosted separately from your GitLab application servers, you can do this using the PostgreSQL binaries packaged diff --git a/doc/administration/raketasks/incoming_email.md b/doc/administration/raketasks/incoming_email.md index d5766c0dd56..0f8a0592c16 100644 --- a/doc/administration/raketasks/incoming_email.md +++ b/doc/administration/raketasks/incoming_email.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/108279) in GitLab 15.9. diff --git a/doc/administration/raketasks/ldap.md b/doc/administration/raketasks/ldap.md index eb8c2514d09..e3473b9b897 100644 --- a/doc/administration/raketasks/ldap.md +++ b/doc/administration/raketasks/ldap.md @@ -42,7 +42,7 @@ rake gitlab:ldap:check[50] DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/14735) in GitLab 12.2. diff --git a/doc/administration/raketasks/maintenance.md b/doc/administration/raketasks/maintenance.md index 734fc658ecc..7910420bb8a 100644 --- a/doc/administration/raketasks/maintenance.md +++ b/doc/administration/raketasks/maintenance.md @@ -81,7 +81,7 @@ Gitaly DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/20501) in GitLab 12.6. > - Moved to GitLab Premium in 13.9. diff --git a/doc/administration/read_only_gitlab.md b/doc/administration/read_only_gitlab.md index c061fa475a2..422484daa58 100644 --- a/doc/administration/read_only_gitlab.md +++ b/doc/administration/read_only_gitlab.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: In GitLab 13.9 and later, the recommended method to diff --git a/doc/administration/redis/index.md b/doc/administration/redis/index.md index 9508f4727b9..dce42b912a0 100644 --- a/doc/administration/redis/index.md +++ b/doc/administration/redis/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Based on your infrastructure setup and how you have installed GitLab, there are multiple ways to configure Redis. diff --git a/doc/administration/redis/replication_and_failover.md b/doc/administration/redis/replication_and_failover.md index 98f59229259..05cd0ee92ec 100644 --- a/doc/administration/redis/replication_and_failover.md +++ b/doc/administration/redis/replication_and_failover.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This documentation is for the Linux package. To use your own non-bundled Redis, see [Redis replication and failover providing your own instance](replication_and_failover_external.md). diff --git a/doc/administration/redis/replication_and_failover_external.md b/doc/administration/redis/replication_and_failover_external.md index 9d60de7c822..25e2a99e69c 100644 --- a/doc/administration/redis/replication_and_failover_external.md +++ b/doc/administration/redis/replication_and_failover_external.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you're hosting GitLab on a cloud provider, you can optionally use a managed service for Redis. For example, AWS offers ElastiCache that runs Redis. diff --git a/doc/administration/redis/standalone.md b/doc/administration/redis/standalone.md index 0724350b8de..c49d9ecec4c 100644 --- a/doc/administration/redis/standalone.md +++ b/doc/administration/redis/standalone.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The Linux package can be used to configure a standalone Redis server. In this configuration, Redis is not scaled, and represents a single diff --git a/doc/administration/redis/troubleshooting.md b/doc/administration/redis/troubleshooting.md index e55f866bc9e..7ec6414bf45 100644 --- a/doc/administration/redis/troubleshooting.md +++ b/doc/administration/redis/troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed There are a lot of moving parts that must be taken care carefully in order for the HA setup to work as expected. diff --git a/doc/administration/reference_architectures/10k_users.md b/doc/administration/reference_architectures/10k_users.md index 098f4276311..5b0db5b91dc 100644 --- a/doc/administration/reference_architectures/10k_users.md +++ b/doc/administration/reference_architectures/10k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 10,000 users with notable headroom. diff --git a/doc/administration/reference_architectures/1k_users.md b/doc/administration/reference_architectures/1k_users.md index 518253f1dea..5499166ded7 100644 --- a/doc/administration/reference_architectures/1k_users.md +++ b/doc/administration/reference_architectures/1k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 1,000 users with notable headroom (non-HA standalone). @@ -105,7 +105,7 @@ performance and reliability at an increased complexity cost. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can leverage Elasticsearch and [enable advanced search](../../integration/advanced_search/elasticsearch.md) for faster, more advanced code search across your entire GitLab instance. diff --git a/doc/administration/reference_architectures/25k_users.md b/doc/administration/reference_architectures/25k_users.md index 2ce966daba0..9206dea764e 100644 --- a/doc/administration/reference_architectures/25k_users.md +++ b/doc/administration/reference_architectures/25k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 25,000 users with notable headroom. diff --git a/doc/administration/reference_architectures/2k_users.md b/doc/administration/reference_architectures/2k_users.md index 946b8c70b83..855e049f32a 100644 --- a/doc/administration/reference_architectures/2k_users.md +++ b/doc/administration/reference_architectures/2k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 2,000 users with notable headroom (non-HA). @@ -1070,7 +1070,7 @@ While sharing the job logs through NFS is supported, it's recommended to avoid t DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can leverage Elasticsearch and [enable advanced search](../../integration/advanced_search/elasticsearch.md) for faster, more advanced code search across your entire GitLab instance. diff --git a/doc/administration/reference_architectures/3k_users.md b/doc/administration/reference_architectures/3k_users.md index cf5e8656b78..bd3b7f8aab5 100644 --- a/doc/administration/reference_architectures/3k_users.md +++ b/doc/administration/reference_architectures/3k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 3,000 users with notable headroom. diff --git a/doc/administration/reference_architectures/50k_users.md b/doc/administration/reference_architectures/50k_users.md index ccd1f1f2c6c..affef410136 100644 --- a/doc/administration/reference_architectures/50k_users.md +++ b/doc/administration/reference_architectures/50k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 50,000 users with notable headroom. diff --git a/doc/administration/reference_architectures/5k_users.md b/doc/administration/reference_architectures/5k_users.md index 20464f2ec17..3e79b6ce247 100644 --- a/doc/administration/reference_architectures/5k_users.md +++ b/doc/administration/reference_architectures/5k_users.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page describes the GitLab reference architecture designed for the load of up to 5,000 users with notable headroom. diff --git a/doc/administration/reference_architectures/index.md b/doc/administration/reference_architectures/index.md index bcdfcf46036..9a861039d19 100644 --- a/doc/administration/reference_architectures/index.md +++ b/doc/administration/reference_architectures/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The GitLab Reference Architectures have been designed and tested by the GitLab Quality Engineering and Support teams to provide recommended deployments at scale. diff --git a/doc/administration/reply_by_email_postfix_setup.md b/doc/administration/reply_by_email_postfix_setup.md index b39940ad944..5425b71491f 100644 --- a/doc/administration/reply_by_email_postfix_setup.md +++ b/doc/administration/reply_by_email_postfix_setup.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document takes you through the steps of setting up a basic Postfix mail server with IMAP authentication on Ubuntu, to be used with [incoming email](incoming_email.md). diff --git a/doc/administration/reporting/git_abuse_rate_limit.md b/doc/administration/reporting/git_abuse_rate_limit.md index b65a5f37e64..3a742c894d1 100644 --- a/doc/administration/reporting/git_abuse_rate_limit.md +++ b/doc/administration/reporting/git_abuse_rate_limit.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/8066) in GitLab 15.2 [with a flag](../../administration/feature_flags.md) named `git_abuse_rate_limit_feature_flag`. Disabled by default. > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/394996) in GitLab 15.11. Feature flag `git_abuse_rate_limit_feature_flag` removed. diff --git a/doc/administration/reporting/ip_addr_restrictions.md b/doc/administration/reporting/ip_addr_restrictions.md index 7d8160168ce..e178e8d66b2 100644 --- a/doc/administration/reporting/ip_addr_restrictions.md +++ b/doc/administration/reporting/ip_addr_restrictions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed IP address restrictions help prevent malicious users hiding their activities behind multiple IP addresses. diff --git a/doc/administration/reporting/spamcheck.md b/doc/administration/reporting/spamcheck.md index 5b75d99c316..fa62c02e264 100644 --- a/doc/administration/reporting/spamcheck.md +++ b/doc/administration/reporting/spamcheck.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6259) in GitLab 14.8. diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md index 68a73deec8c..9683a4b2770 100644 --- a/doc/administration/repository_checks.md +++ b/doc/administration/repository_checks.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can use [`git fsck`](https://git-scm.com/docs/git-fsck) to verify the integrity of all data committed to a repository. GitLab administrators can: diff --git a/doc/administration/repository_storage_paths.md b/doc/administration/repository_storage_paths.md index da48ca60448..bea726524a5 100644 --- a/doc/administration/repository_storage_paths.md +++ b/doc/administration/repository_storage_paths.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab stores [repositories](../user/project/repository/index.md) on repository storage. Repository storage is either: diff --git a/doc/administration/restart_gitlab.md b/doc/administration/restart_gitlab.md index 8c4f27a4029..dea9ce624fa 100644 --- a/doc/administration/restart_gitlab.md +++ b/doc/administration/restart_gitlab.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Depending on how you installed GitLab, there are different methods to restart its services. diff --git a/doc/administration/review_abuse_reports.md b/doc/administration/review_abuse_reports.md index e24b65d8ad8..badbf327094 100644 --- a/doc/administration/review_abuse_reports.md +++ b/doc/administration/review_abuse_reports.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed View and resolve abuse reports from GitLab users. diff --git a/doc/administration/review_spam_logs.md b/doc/administration/review_spam_logs.md index f727568ff8a..61fc6a1eec5 100644 --- a/doc/administration/review_spam_logs.md +++ b/doc/administration/review_spam_logs.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab tracks user activity and flags certain behavior for potential spam. diff --git a/doc/administration/secure_files.md b/doc/administration/secure_files.md index 63047ac91c3..f311f40d9df 100644 --- a/doc/administration/secure_files.md +++ b/doc/administration/secure_files.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78227) in GitLab 14.8 [with a flag](feature_flags.md) named `ci_secure_files`. Disabled by default. > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/issues/350748) in GitLab 15.7. Feature flag `ci_secure_files` removed. @@ -93,7 +93,7 @@ are stored locally, follow the steps below. DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Instead of storing Secure Files on disk, you should use [one of the supported object storage options](object_storage.md#supported-object-storage-providers). This configuration relies on valid credentials to be configured already. diff --git a/doc/administration/settings/account_and_limit_settings.md b/doc/administration/settings/account_and_limit_settings.md index 1c327a35611..3b7d5d258a2 100644 --- a/doc/administration/settings/account_and_limit_settings.md +++ b/doc/administration/settings/account_and_limit_settings.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Default projects limit @@ -105,7 +105,7 @@ You can also configure the prefix by using the DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Repositories in your GitLab instance can grow quickly, especially if you are using LFS. Their size can grow exponentially, rapidly consuming available storage. @@ -187,7 +187,7 @@ Users can select the **Remember me** checkbox on sign-in, and their session will DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/296669) in GitLab 13.9. > - It's deployed behind a feature flag, disabled by default. @@ -209,7 +209,7 @@ To set a limit on how long these sessions are valid: DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/1007) in GitLab 14.6 [with a flag](../../administration/feature_flags.md) named `ff_limit_ssh_key_lifetime`. Disabled by default. > - [Enabled on self-managed](https://gitlab.com/gitlab-org/gitlab/-/issues/346753) in GitLab 14.6. @@ -250,7 +250,7 @@ When a user's SSH key becomes invalid they can delete and re-add the same key ag DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3649) in GitLab 12.6. @@ -288,7 +288,7 @@ Once a lifetime for access tokens is set, GitLab: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/24605) in GitLab 12.7. @@ -354,7 +354,7 @@ By default, newly created users have a public profile. GitLab administrators can DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/26053) in GitLab 16.1 [with a flag](../../administration/feature_flags.md) named `deleting_account_disabled_for_users`. Enabled by default. diff --git a/doc/administration/settings/continuous_integration.md b/doc/administration/settings/continuous_integration.md index 73ea6cc6a8d..d8ba43d78a2 100644 --- a/doc/administration/settings/continuous_integration.md +++ b/doc/administration/settings/continuous_integration.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The [Admin Area](index.md) has the instance settings for Auto DevOps, runners, and job artifacts. @@ -285,7 +285,7 @@ so you can view job artifact pages directly: DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Moved](https://gitlab.com/gitlab-org/gitlab/-/issues/352316) from GitLab Premium to GitLab Ultimate in 15.0. > - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/389467) in GitLab 15.9. @@ -328,7 +328,7 @@ To select a CI/CD template for the required pipeline configuration: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab administrators can disable the forwarding of Maven requests to [Maven Central](https://search.maven.org/). @@ -344,7 +344,7 @@ To disable forwarding Maven requests: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab administrators can disable the forwarding of npm requests to [npmjs.com](https://www.npmjs.com/). @@ -360,7 +360,7 @@ To disable it: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab administrators can disable the forwarding of PyPI requests to [pypi.org](https://pypi.org/). diff --git a/doc/administration/settings/deprecated_api_rate_limits.md b/doc/administration/settings/deprecated_api_rate_limits.md index f3011ec58eb..a4a1e2979b3 100644 --- a/doc/administration/settings/deprecated_api_rate_limits.md +++ b/doc/administration/settings/deprecated_api_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68645) in GitLab 14.4. diff --git a/doc/administration/settings/email.md b/doc/administration/settings/email.md index 2e126201332..80c8123e8b5 100644 --- a/doc/administration/settings/email.md +++ b/doc/administration/settings/email.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can customize some of the content in emails sent from your GitLab instance. @@ -20,7 +20,7 @@ The logo in the header of some emails can be customized, see the [logo customiza DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed By default, GitLab overrides the email address in notification emails with the email address of the issue, merge request, or comment author. Enable this setting to include the author's email @@ -38,7 +38,7 @@ To include the author's email address in the email body: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab can send email in multipart format (HTML and plain text) or plain text only. @@ -54,7 +54,7 @@ To enable multipart email: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22560) in GitLab 11.5. @@ -78,7 +78,7 @@ recognized by GitLab. This can directly conflict with certain [Push rules](../.. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can add additional text at the bottom of any email that GitLab sends. This additional text can be used for legal, auditing, or compliance reasons, for example. @@ -107,7 +107,7 @@ To disable these notifications: DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/355964) in GitLab 15.9 [with a flag](../../administration/feature_flags.md) named `deactivation_email_additional_text`. Disabled by default. > - [Enabled on self-managed and GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/111882) in GitLab 15.9. diff --git a/doc/administration/settings/external_authorization.md b/doc/administration/settings/external_authorization.md index 95e42a39894..76d991caab4 100644 --- a/doc/administration/settings/external_authorization.md +++ b/doc/administration/settings/external_authorization.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Moved](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/27056) from GitLab Premium to GitLab Free in 11.10. diff --git a/doc/administration/settings/files_api_rate_limits.md b/doc/administration/settings/files_api_rate_limits.md index 87bb599eb60..b4b0e37fd67 100644 --- a/doc/administration/settings/files_api_rate_limits.md +++ b/doc/administration/settings/files_api_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68561) in GitLab 14.3. > - [Generally available](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75918) in GitLab 14.6. [Feature flag `files_api_throttling`](https://gitlab.com/gitlab-org/gitlab/-/issues/338903) removed. diff --git a/doc/administration/settings/floc.md b/doc/administration/settings/floc.md index f0bd7d572f5..d76eefee4e5 100644 --- a/doc/administration/settings/floc.md +++ b/doc/administration/settings/floc.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60933) in GitLab 13.12. diff --git a/doc/administration/settings/git_lfs_rate_limits.md b/doc/administration/settings/git_lfs_rate_limits.md index 7dc33861fb0..91d67b3c19f 100644 --- a/doc/administration/settings/git_lfs_rate_limits.md +++ b/doc/administration/settings/git_lfs_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed [Git LFS (Large File Storage)](../../topics/git/lfs/index.md) is a Git extension for handling large files. If you use Git LFS in your repository, common Git operations diff --git a/doc/administration/settings/gitaly_timeouts.md b/doc/administration/settings/gitaly_timeouts.md index aaa905032c7..51bed3a072b 100644 --- a/doc/administration/settings/gitaly_timeouts.md +++ b/doc/administration/settings/gitaly_timeouts.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed [Gitaly](../gitaly/index.md) provides two types of configurable timeouts: diff --git a/doc/administration/settings/help_page.md b/doc/administration/settings/help_page.md index 638b9b7789f..81e52c38af4 100644 --- a/doc/administration/settings/help_page.md +++ b/doc/administration/settings/help_page.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed In large organizations, it is useful to have information about who to contact or where to go for help. You can customize and display this information on the GitLab `/help` page and on diff --git a/doc/administration/settings/import_and_export_settings.md b/doc/administration/settings/import_and_export_settings.md index a5f43688f13..a6030d35b57 100644 --- a/doc/administration/settings/import_and_export_settings.md +++ b/doc/administration/settings/import_and_export_settings.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Settings for import- and export-related features. diff --git a/doc/administration/settings/import_export_rate_limits.md b/doc/administration/settings/import_export_rate_limits.md index 4d397c368e2..785870e93ae 100644 --- a/doc/administration/settings/import_export_rate_limits.md +++ b/doc/administration/settings/import_export_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35728) in GitLab 13.2. diff --git a/doc/administration/settings/incident_management_rate_limits.md b/doc/administration/settings/incident_management_rate_limits.md index e36f905a1e1..629fbc13f1f 100644 --- a/doc/administration/settings/incident_management_rate_limits.md +++ b/doc/administration/settings/incident_management_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17859) in GitLab 12.5. diff --git a/doc/administration/settings/index.md b/doc/administration/settings/index.md index ff9380973bd..8b8dc8750aa 100644 --- a/doc/administration/settings/index.md +++ b/doc/administration/settings/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed As an administrator of a GitLab self-managed instance, you can manage the behavior of your deployment. diff --git a/doc/administration/settings/instance_template_repository.md b/doc/administration/settings/instance_template_repository.md index 041e6d6a347..3d3bdb516d9 100644 --- a/doc/administration/settings/instance_template_repository.md +++ b/doc/administration/settings/instance_template_repository.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Improved](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52360) to behave like group-level templates in GitLab 13.9. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/321247) in GitLab 14.0. diff --git a/doc/administration/settings/jira_cloud_app.md b/doc/administration/settings/jira_cloud_app.md index 6251082599a..1003bf675cf 100644 --- a/doc/administration/settings/jira_cloud_app.md +++ b/doc/administration/settings/jira_cloud_app.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: This page contains administrator documentation for the GitLab for Jira Cloud app. For user documentation, see [GitLab for Jira Cloud app](../../integration/jira/connect-app.md). diff --git a/doc/administration/settings/jira_cloud_app_troubleshooting.md b/doc/administration/settings/jira_cloud_app_troubleshooting.md index b5144d9bc3b..84a8c0713ba 100644 --- a/doc/administration/settings/jira_cloud_app_troubleshooting.md +++ b/doc/administration/settings/jira_cloud_app_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed When administering the GitLab for Jira Cloud app, you might encounter the following issues. diff --git a/doc/administration/settings/localization.md b/doc/administration/settings/localization.md index a63342b3bea..e48ac74c1b8 100644 --- a/doc/administration/settings/localization.md +++ b/doc/administration/settings/localization.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed As an administrator of a GitLab self-managed instance, you can manage the behavior of your deployment. diff --git a/doc/administration/settings/package_registry_rate_limits.md b/doc/administration/settings/package_registry_rate_limits.md index 1bae5a19246..70a7e09c7f4 100644 --- a/doc/administration/settings/package_registry_rate_limits.md +++ b/doc/administration/settings/package_registry_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed With the [GitLab package registry](../../user/packages/package_registry/index.md), you can use GitLab as a private or public registry for a variety of common package managers. You can diff --git a/doc/administration/settings/project_integration_management.md b/doc/administration/settings/project_integration_management.md index 78634a3da89..45805d82db9 100644 --- a/doc/administration/settings/project_integration_management.md +++ b/doc/administration/settings/project_integration_management.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: This page contains administrator documentation for project integrations. For user documentation, see [Project integrations](../../user/project/integrations/index.md). diff --git a/doc/administration/settings/protected_paths.md b/doc/administration/settings/protected_paths.md index e3c5230d5ef..f775bfbeb31 100644 --- a/doc/administration/settings/protected_paths.md +++ b/doc/administration/settings/protected_paths.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Rate limiting is a technique that improves the security and durability of a web application. For more details, see [Rate limits](../../security/rate_limits.md). diff --git a/doc/administration/settings/push_event_activities_limit.md b/doc/administration/settings/push_event_activities_limit.md index 1d50204e7e8..0e61c205d96 100644 --- a/doc/administration/settings/push_event_activities_limit.md +++ b/doc/administration/settings/push_event_activities_limit.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/31007) in GitLab 12.4. diff --git a/doc/administration/settings/rate_limit_on_issues_creation.md b/doc/administration/settings/rate_limit_on_issues_creation.md index 2bc531e96b3..22a0e905e85 100644 --- a/doc/administration/settings/rate_limit_on_issues_creation.md +++ b/doc/administration/settings/rate_limit_on_issues_creation.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28129) in GitLab 12.10. diff --git a/doc/administration/settings/rate_limit_on_members_api.md b/doc/administration/settings/rate_limit_on_members_api.md index 6d345da6be2..5a6911d2bca 100644 --- a/doc/administration/settings/rate_limit_on_members_api.md +++ b/doc/administration/settings/rate_limit_on_members_api.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/140633) in GitLab 16.9. diff --git a/doc/administration/settings/rate_limit_on_notes_creation.md b/doc/administration/settings/rate_limit_on_notes_creation.md index 1ef37637fc3..94d09576bbf 100644 --- a/doc/administration/settings/rate_limit_on_notes_creation.md +++ b/doc/administration/settings/rate_limit_on_notes_creation.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/53637) in GitLab 13.9. diff --git a/doc/administration/settings/rate_limit_on_pipelines_creation.md b/doc/administration/settings/rate_limit_on_pipelines_creation.md index 1a470be23b0..0137f1f72ea 100644 --- a/doc/administration/settings/rate_limit_on_pipelines_creation.md +++ b/doc/administration/settings/rate_limit_on_pipelines_creation.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/362475) in GitLab 15.0. diff --git a/doc/administration/settings/rate_limit_on_projects_api.md b/doc/administration/settings/rate_limit_on_projects_api.md index 49e31579fc1..6a6fea8ed2b 100644 --- a/doc/administration/settings/rate_limit_on_projects_api.md +++ b/doc/administration/settings/rate_limit_on_projects_api.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/112283) in GitLab 15.10 with a [flag](../feature_flags.md) named `rate_limit_for_unauthenticated_projects_api_access`. Disabled by default. > - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/391922) on May 08, 2023. diff --git a/doc/administration/settings/rate_limit_on_users_api.md b/doc/administration/settings/rate_limit_on_users_api.md index ee96fc0c8c5..cad09a8e2ca 100644 --- a/doc/administration/settings/rate_limit_on_users_api.md +++ b/doc/administration/settings/rate_limit_on_users_api.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78364) in GitLab 14.8. diff --git a/doc/administration/settings/rate_limits_on_git_ssh_operations.md b/doc/administration/settings/rate_limits_on_git_ssh_operations.md index 1dc451dd156..87ada453eff 100644 --- a/doc/administration/settings/rate_limits_on_git_ssh_operations.md +++ b/doc/administration/settings/rate_limits_on_git_ssh_operations.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/78373) in GitLab 14.7 [with a flag](../feature_flags.md) named `rate_limit_gitlab_shell`. Available by default without a feature flag from 15.8. diff --git a/doc/administration/settings/rate_limits_on_raw_endpoints.md b/doc/administration/settings/rate_limits_on_raw_endpoints.md index d6f93314f47..0dfb5d4080b 100644 --- a/doc/administration/settings/rate_limits_on_raw_endpoints.md +++ b/doc/administration/settings/rate_limits_on_raw_endpoints.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/30635) in GitLab 12.2. diff --git a/doc/administration/settings/scim_setup.md b/doc/administration/settings/scim_setup.md index d2970c73d44..a044cf60556 100644 --- a/doc/administration/settings/scim_setup.md +++ b/doc/administration/settings/scim_setup.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/8902) in GitLab 15.8. diff --git a/doc/administration/settings/security_and_compliance.md b/doc/administration/settings/security_and_compliance.md index 74cf2a7dba7..6e0c6020fd4 100644 --- a/doc/administration/settings/security_and_compliance.md +++ b/doc/administration/settings/security_and_compliance.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The settings for package metadata synchronization are located in the [Admin Area](index.md). diff --git a/doc/administration/settings/security_contact_information.md b/doc/administration/settings/security_contact_information.md index 371f0eb4d28..edce0ef1b77 100644 --- a/doc/administration/settings/security_contact_information.md +++ b/doc/administration/settings/security_contact_information.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/433210) in GitLab 16.7. diff --git a/doc/administration/settings/sidekiq_job_limits.md b/doc/administration/settings/sidekiq_job_limits.md index be1337f5a8b..a0c6ece333e 100644 --- a/doc/administration/settings/sidekiq_job_limits.md +++ b/doc/administration/settings/sidekiq_job_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68982) in GitLab 14.3. diff --git a/doc/administration/settings/sign_in_restrictions.md b/doc/administration/settings/sign_in_restrictions.md index eb05618eaf7..d0cb7ed2acc 100644 --- a/doc/administration/settings/sign_in_restrictions.md +++ b/doc/administration/settings/sign_in_restrictions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can use **Sign-in restrictions** to customize authentication restrictions for web interfaces as well as Git over HTTP(S). diff --git a/doc/administration/settings/sign_up_restrictions.md b/doc/administration/settings/sign_up_restrictions.md index 94729273099..c9b4cea0023 100644 --- a/doc/administration/settings/sign_up_restrictions.md +++ b/doc/administration/settings/sign_up_restrictions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can enforce the following restrictions on sign ups: @@ -145,7 +145,7 @@ the minimum number of characters a user must have in their password using the Gi DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/354965) in GitLab 15.2. diff --git a/doc/administration/settings/slack_app.md b/doc/administration/settings/slack_app.md index 5fe74a7ac02..d27677776f8 100644 --- a/doc/administration/settings/slack_app.md +++ b/doc/administration/settings/slack_app.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/358872) for self-managed in GitLab 16.2. diff --git a/doc/administration/settings/terms.md b/doc/administration/settings/terms.md index 365dbba35c0..026d7fe2855 100644 --- a/doc/administration/settings/terms.md +++ b/doc/administration/settings/terms.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed An administrator can enforce acceptance of a terms of service and privacy policy. When this option is enabled, new and existing users must accept the terms. diff --git a/doc/administration/settings/terraform_limits.md b/doc/administration/settings/terraform_limits.md index 5470e711f27..a621d18d478 100644 --- a/doc/administration/settings/terraform_limits.md +++ b/doc/administration/settings/terraform_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/352951) in GitLab 15.7. diff --git a/doc/administration/settings/third_party_offers.md b/doc/administration/settings/third_party_offers.md index 4a32a3d644e..1ff49b4b02e 100644 --- a/doc/administration/settings/third_party_offers.md +++ b/doc/administration/settings/third_party_offers.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/20379) in GitLab 11.1. diff --git a/doc/administration/settings/usage_statistics.md b/doc/administration/settings/usage_statistics.md index 8a31c06a061..b8a54de4edd 100644 --- a/doc/administration/settings/usage_statistics.md +++ b/doc/administration/settings/usage_statistics.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab Inc. periodically collects information about your instance in order to perform various actions. diff --git a/doc/administration/settings/user_and_ip_rate_limits.md b/doc/administration/settings/user_and_ip_rate_limits.md index bd83ed85b9e..8f25c89f8f6 100644 --- a/doc/administration/settings/user_and_ip_rate_limits.md +++ b/doc/administration/settings/user_and_ip_rate_limits.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Rate limiting is a common technique used to improve the security and durability of a web application. For more details, see diff --git a/doc/administration/settings/visibility_and_access_controls.md b/doc/administration/settings/visibility_and_access_controls.md index 97fb55016c2..a04d0d5c0a4 100644 --- a/doc/administration/settings/visibility_and_access_controls.md +++ b/doc/administration/settings/visibility_and_access_controls.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab enables users with administrator access to enforce specific controls on branches, projects, snippets, groups, and more. @@ -40,7 +40,7 @@ on the instance. To alter which roles have permission to create projects: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - User interface [changed](https://gitlab.com/gitlab-org/gitlab/-/issues/352960) in GitLab 15.1. @@ -59,7 +59,7 @@ By default both administrators and anyone with the **Owner** role can delete a p DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/255449) in GitLab 14.2 for groups created after August 12, 2021. > - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/352960) from default delayed project deletion in GitLab 15.1. diff --git a/doc/administration/sidekiq/extra_sidekiq_processes.md b/doc/administration/sidekiq/extra_sidekiq_processes.md index 786bab47b2e..562e4cb6165 100644 --- a/doc/administration/sidekiq/extra_sidekiq_processes.md +++ b/doc/administration/sidekiq/extra_sidekiq_processes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab allows you to start multiple Sidekiq processes to process background jobs at a higher rate on a single instance. By default, Sidekiq starts one worker diff --git a/doc/administration/sidekiq/index.md b/doc/administration/sidekiq/index.md index fe9a2ca3240..73a6cf5cecf 100644 --- a/doc/administration/sidekiq/index.md +++ b/doc/administration/sidekiq/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can configure an external Sidekiq instance by using the Sidekiq that's bundled in the GitLab package. Sidekiq requires connection to the Redis, PostgreSQL, and Gitaly instances. diff --git a/doc/administration/sidekiq/sidekiq_health_check.md b/doc/administration/sidekiq/sidekiq_health_check.md index 4d5f2f560bf..4c164e6eee7 100644 --- a/doc/administration/sidekiq/sidekiq_health_check.md +++ b/doc/administration/sidekiq/sidekiq_health_check.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab provides liveness and readiness probes to indicate service health and reachability to the Sidekiq cluster. These endpoints diff --git a/doc/administration/sidekiq/sidekiq_job_migration.md b/doc/administration/sidekiq/sidekiq_job_migration.md index be2538ae230..a455ceae4ef 100644 --- a/doc/administration/sidekiq/sidekiq_job_migration.md +++ b/doc/administration/sidekiq/sidekiq_job_migration.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: This operation should be very uncommon. We do not recommend it for the vast majority of GitLab instances. diff --git a/doc/administration/sidekiq/sidekiq_troubleshooting.md b/doc/administration/sidekiq/sidekiq_troubleshooting.md index e420f0f2f31..be33ccf4358 100644 --- a/doc/administration/sidekiq/sidekiq_troubleshooting.md +++ b/doc/administration/sidekiq/sidekiq_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Sidekiq is the background job processor GitLab uses to asynchronously run tasks. When things go wrong it can be difficult to troubleshoot. These diff --git a/doc/administration/silent_mode/index.md b/doc/administration/silent_mode/index.md index 8883ac64053..1edbef835b1 100644 --- a/doc/administration/silent_mode/index.md +++ b/doc/administration/silent_mode/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/9826) in GitLab 15.11. This feature was an [Experiment](../../policy/experiment-beta-support.md#experiment). > - Enabling and disabling Silent Mode through the web UI was [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/131090) in GitLab 16.4. diff --git a/doc/administration/smime_signing_email.md b/doc/administration/smime_signing_email.md index cc2994c385d..bc2e2f19558 100644 --- a/doc/administration/smime_signing_email.md +++ b/doc/administration/smime_signing_email.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Notification emails sent by GitLab can be signed with S/MIME for improved security. diff --git a/doc/administration/snippets/index.md b/doc/administration/snippets/index.md index 781d1a6c0c4..5344f6e2e7b 100644 --- a/doc/administration/snippets/index.md +++ b/doc/administration/snippets/index.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can configure a maximum size for a snippet to prevent abuse. The default limit is 52428800 bytes (50 MB). diff --git a/doc/administration/static_objects_external_storage.md b/doc/administration/static_objects_external_storage.md index 2f550fef4d7..8bccb865a4c 100644 --- a/doc/administration/static_objects_external_storage.md +++ b/doc/administration/static_objects_external_storage.md @@ -8,7 +8,7 @@ info: "To determine the technical writer assigned to the Stage/Group associated DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/31025) in GitLab 12.3. diff --git a/doc/administration/system_hooks.md b/doc/administration/system_hooks.md index d2f43ccc21e..9f14b58f5e8 100644 --- a/doc/administration/system_hooks.md +++ b/doc/administration/system_hooks.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed System hooks (not to be confused with [server hooks](server_hooks.md) or [file hooks](file_hooks.md)) perform HTTP POST requests and are triggered on the following events: diff --git a/doc/administration/terraform_state.md b/doc/administration/terraform_state.md index 15a2a6e1e39..9cafd453797 100644 --- a/doc/administration/terraform_state.md +++ b/doc/administration/terraform_state.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/groups/gitlab-org/-/epics/2673) in GitLab 12.10. @@ -98,7 +98,7 @@ For self-compiled installations: DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Instead of storing Terraform state files on disk, we recommend the use of [one of the supported object storage options](object_storage.md#supported-object-storage-providers). diff --git a/doc/administration/timezone.md b/doc/administration/timezone.md index c101c33956c..e0ee4a8aeea 100644 --- a/doc/administration/timezone.md +++ b/doc/administration/timezone.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed The global time zone configuration parameter can be changed in `config/gitlab.yml`: diff --git a/doc/administration/troubleshooting/diagnostics_tools.md b/doc/administration/troubleshooting/diagnostics_tools.md index 14cacfc0a1c..4a30e0a9295 100644 --- a/doc/administration/troubleshooting/diagnostics_tools.md +++ b/doc/administration/troubleshooting/diagnostics_tools.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed These are some of the diagnostics tools the GitLab Support team uses during troubleshooting. They are listed here for transparency, and for users with experience diff --git a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md index 42f86e46ac7..253e493ad49 100644 --- a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md +++ b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This was the GitLab Support Team's collection of information regarding the GitLab Rails console, for use while troubleshooting. It is listed here for posterity, diff --git a/doc/administration/troubleshooting/index.md b/doc/administration/troubleshooting/index.md index cf0f29e3a92..5284831604c 100644 --- a/doc/administration/troubleshooting/index.md +++ b/doc/administration/troubleshooting/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page documents a collection of resources to help you troubleshoot a GitLab installation. diff --git a/doc/administration/troubleshooting/linux_cheat_sheet.md b/doc/administration/troubleshooting/linux_cheat_sheet.md index 4f5e88c3e6a..f2f31282e86 100644 --- a/doc/administration/troubleshooting/linux_cheat_sheet.md +++ b/doc/administration/troubleshooting/linux_cheat_sheet.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This is the GitLab Support Team's collection of information regarding Linux, that they sometimes use while troubleshooting. It is listed here for transparency, diff --git a/doc/administration/troubleshooting/postgresql.md b/doc/administration/troubleshooting/postgresql.md index 01e6d8dfba4..0c033eea347 100644 --- a/doc/administration/troubleshooting/postgresql.md +++ b/doc/administration/troubleshooting/postgresql.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains information about PostgreSQL the GitLab Support team uses when troubleshooting. GitLab makes this information public, so that anyone can diff --git a/doc/administration/troubleshooting/test_environments.md b/doc/administration/troubleshooting/test_environments.md index 410e3c4e26c..d7f265c1185 100644 --- a/doc/administration/troubleshooting/test_environments.md +++ b/doc/administration/troubleshooting/test_environments.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This is the GitLab Support Team's collection of information regarding testing environments, for use while troubleshooting. It is listed here for transparency, and it may be useful diff --git a/doc/administration/uploads.md b/doc/administration/uploads.md index f891e4081c2..f213c373ac1 100644 --- a/doc/administration/uploads.md +++ b/doc/administration/uploads.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Uploads represent all user data that may be sent to GitLab as a single file. For example, avatars and note attachments are uploads. Uploads are integral to GitLab functionality and therefore cannot be disabled. @@ -62,7 +62,7 @@ _The uploads are stored by default in DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed If you don't want to use the local disk where GitLab is installed to store the uploads, you can use an object storage provider like AWS S3 instead. diff --git a/doc/administration/user_cohorts.md b/doc/administration/user_cohorts.md index 778c73bbe52..f11d46cd8d4 100644 --- a/doc/administration/user_cohorts.md +++ b/doc/administration/user_cohorts.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can analyze your users' GitLab activities over time. diff --git a/doc/administration/user_settings.md b/doc/administration/user_settings.md index bcd6b2ff1f4..8e425cb87bd 100644 --- a/doc/administration/user_settings.md +++ b/doc/administration/user_settings.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed GitLab administrators can modify user settings for the entire GitLab instance. diff --git a/doc/administration/wikis/index.md b/doc/administration/wikis/index.md index 978486c9213..5719f876db2 100644 --- a/doc/administration/wikis/index.md +++ b/doc/administration/wikis/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Adjust the wiki settings of your GitLab instance. diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md index 31340ab5782..84ce099c158 100644 --- a/doc/api/graphql/reference/index.md +++ b/doc/api/graphql/reference/index.md @@ -8991,6 +8991,7 @@ Input type: `WorkItemUpdateInput` | `startAndDueDateWidget` | [`WorkItemWidgetStartAndDueDateUpdateInput`](#workitemwidgetstartandduedateupdateinput) | Input for start and due date widget. | | `stateEvent` | [`WorkItemStateEvent`](#workitemstateevent) | Close or reopen a work item. | | `statusWidget` | [`StatusInput`](#statusinput) | Input for status widget. | +| `timeTrackingWidget` | [`WorkItemWidgetTimeTrackingInput`](#workitemwidgettimetrackinginput) | Input for time tracking widget. | | `title` | [`String`](#string) | Title of the work item. | | `weightWidget` | [`WorkItemWidgetWeightInput`](#workitemwidgetweightinput) | Input for weight widget. | @@ -14344,6 +14345,31 @@ The edge type for [`WorkItem`](#workitem). | `cursor` | [`String!`](#string) | A cursor for use in pagination. | | `node` | [`WorkItem`](#workitem) | The item at the end of the edge. | +#### `WorkItemTimelogConnection` + +The connection type for [`WorkItemTimelog`](#workitemtimelog). + +##### Fields + +| Name | Type | Description | +| ---- | ---- | ----------- | +| `count` | [`Int!`](#int) | Total count of collection. | +| `edges` | [`[WorkItemTimelogEdge]`](#workitemtimelogedge) | A list of edges. | +| `nodes` | [`[WorkItemTimelog]`](#workitemtimelog) | A list of nodes. | +| `pageInfo` | [`PageInfo!`](#pageinfo) | Information to aid in pagination. | +| `totalSpentTime` | [`BigInt!`](#bigint) | Total time spent in seconds. | + +#### `WorkItemTimelogEdge` + +The edge type for [`WorkItemTimelog`](#workitemtimelog). + +##### Fields + +| Name | Type | Description | +| ---- | ---- | ----------- | +| `cursor` | [`String!`](#string) | A cursor for use in pagination. | +| `node` | [`WorkItemTimelog`](#workitemtimelog) | The item at the end of the edge. | + #### `WorkItemTypeConnection` The connection type for [`WorkItemType`](#workitemtype). @@ -30017,6 +30043,20 @@ Represents total number of work items for the represented states. | `closed` | [`Int`](#int) | Number of work items with state CLOSED for the project or group. | | `opened` | [`Int`](#int) | Number of work items with state OPENED for the project or group. | +### `WorkItemTimelog` + +#### Fields + +| Name | Type | Description | +| ---- | ---- | ----------- | +| `id` | [`ID!`](#id) | Internal ID of the timelog. | +| `note` | [`Note`](#note) | Note where the quick action was executed to add the logged time. | +| `spentAt` | [`Time`](#time) | Timestamp of when the time tracked was spent at. | +| `summary` | [`String`](#string) | Summary of how the time was spent. | +| `timeSpent` | [`Int!`](#int) | Time spent displayed in seconds. | +| `user` | [`UserCore!`](#usercore) | User that logged the time. | +| `userPermissions` | [`TimelogPermissions!`](#timelogpermissions) | Permissions for the current user on the resource. | + ### `WorkItemType` #### Fields @@ -30397,9 +30437,9 @@ Represents a time tracking widget. | Name | Type | Description | | ---- | ---- | ----------- | -| `timeEstimate` | [`Int!`](#int) | Time estimate of the work item. | -| `timelogs` | [`TimelogConnection!`](#timelogconnection) | Timelogs on the work item. (see [Connections](#connections)) | -| `totalTimeSpent` | [`Int!`](#int) | Total time (in seconds) reported as spent on the work item. | +| `timeEstimate` | [`Int`](#int) | Time estimate of the work item. | +| `timelogs` | [`WorkItemTimelogConnection`](#workitemtimelogconnection) | Timelogs on the work item. (see [Connections](#connections)) | +| `totalTimeSpent` | [`Int`](#int) | Total time (in seconds) reported as spent on the work item. | | `type` | [`WorkItemWidgetType`](#workitemwidgettype) | Widget type. | ### `WorkItemWidgetWeight` @@ -32526,8 +32566,8 @@ Pipeline security report finding sort values. | Value | Description | | ----- | ----------- | -| `SEVERITY_ASC` | Severity in ascending order. | -| `SEVERITY_DESC` | Severity in descending order. | +| `severity_asc` | Severity in ascending order. | +| `severity_desc` | Severity in descending order. | ### `PipelineStatusEnum` @@ -36083,6 +36123,25 @@ Attributes for value stream stage. | `dueDate` | [`Date`](#date) | Due date for the work item. | | `startDate` | [`Date`](#date) | Start date for the work item. | +### `WorkItemWidgetTimeTrackingInput` + +#### Arguments + +| Name | Type | Description | +| ---- | ---- | ----------- | +| `timeEstimate` | [`String`](#string) | Time estimate for the work item in human readable format. For example: 1h 30m. | +| `timelog` | [`WorkItemWidgetTimeTrackingTimelogInput`](#workitemwidgettimetrackingtimeloginput) | Timelog data for time spent on the work item. | + +### `WorkItemWidgetTimeTrackingTimelogInput` + +#### Arguments + +| Name | Type | Description | +| ---- | ---- | ----------- | +| `spentAt` | [`Time`](#time) | Timestamp of when the time tracked was spent at, if not provided would be set to current timestamp. | +| `summary` | [`String`](#string) | Summary of how the time was spent. | +| `timeSpent` | [`String!`](#string) | Amount of time spent in human readable format. For example: 1h 30m. | + ### `WorkItemWidgetWeightInput` #### Arguments diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index 493dc535bcd..f8315db6b5a 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Premium, Ultimate -**Offering:** GitLab.com, Self-managed, GitLab Dedicated +**Offering:** GitLab.com, Self-managed > [Renamed](https://gitlab.com/groups/gitlab-com/-/epics/2150) from "CI/CD minutes" to "compute quota" or "compute minutes" in GitLab 16.1. diff --git a/doc/ci/runners/runner_fleet_dashboard.md b/doc/ci/runners/runner_fleet_dashboard.md index ccb70574abf..e9a3495ffe2 100644 --- a/doc/ci/runners/runner_fleet_dashboard.md +++ b/doc/ci/runners/runner_fleet_dashboard.md @@ -10,7 +10,7 @@ info: >- DETAILS: **Tier:** Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/424495) in GitLab 16.6 diff --git a/doc/integration/mattermost/index.md b/doc/integration/mattermost/index.md index edd4edb8150..02682fd135d 100644 --- a/doc/integration/mattermost/index.md +++ b/doc/integration/mattermost/index.md @@ -6,6 +6,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w # GitLab Mattermost +DETAILS: +**Offering:** Self-managed + You can run a [GitLab Mattermost](https://gitlab.com/gitlab-org/gitlab-mattermost) service on your GitLab server. Mattermost is not part of the single application that GitLab is. There is a good integration between [Mattermost and GitLab](https://mattermost.com/solutions/mattermost-gitlab/), and our Linux package allows you to install it. **However, Mattermost is a separate application from a separate company.** GitLab Support cannot help you with Mattermost-specific questions beyond the integration with GitLab. If you need help with Mattermost itself, see the [community support resources](#community-support-resources). diff --git a/doc/subscriptions/gitlab_com/index.md b/doc/subscriptions/gitlab_com/index.md index acb8d0b9f86..f017057dfc2 100644 --- a/doc/subscriptions/gitlab_com/index.md +++ b/doc/subscriptions/gitlab_com/index.md @@ -333,7 +333,8 @@ To renew your subscription: 1. Review your renewal details and complete the payment process. 1. Select **Confirm purchase**. -Your updated subscription is applied to your namespace on the renewal period start date. It may take up to one day for the renewal to be processed. +Your updated subscription is applied to your namespace. The renewal period start date +is displayed on the group Billing page under **Next subscription term start date**. An invoice is generated for the renewal and available for viewing or download on the [View invoices](https://customers.gitlab.com/receipts) page. If you have difficulty during the renewal process, contact the [Support team](https://support.gitlab.com/hc/en-us/requests/new?ticket_form_id=360000071293) for assistance. diff --git a/doc/update/background_migrations.md b/doc/update/background_migrations.md index 73a50c47b92..d0d255d1c75 100644 --- a/doc/update/background_migrations.md +++ b/doc/update/background_migrations.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - Batched background migrations [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/51332) in GitLab 13.11 [with a flag](../user/feature_flags.md) named `execute_batched_migrations_on_schedule`. Disabled by default. > - Feature flag `execute_batched_migrations_on_schedule` [enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/329511) in GitLab 13.12. diff --git a/doc/update/background_migrations_troubleshooting.md b/doc/update/background_migrations_troubleshooting.md index 45d61119a23..60b89686801 100644 --- a/doc/update/background_migrations_troubleshooting.md +++ b/doc/update/background_migrations_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed diff --git a/doc/update/index.md b/doc/update/index.md index dbb29f6cb6f..89a6507411c 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Upgrading GitLab is a relatively straightforward process, but the complexity can increase based on the installation method you have used, how old your @@ -123,7 +123,7 @@ To address the above two scenarios, it is advised to do the following prior to u DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This section is only applicable if you have enabled the [Elasticsearch integration](../integration/advanced_search/elasticsearch.md). Major releases require all [advanced search migrations](../integration/advanced_search/elasticsearch.md#advanced-search-migrations) diff --git a/doc/update/package/convert_to_ee.md b/doc/update/package/convert_to_ee.md index adb5d053524..437cfaa19ed 100644 --- a/doc/update/package/convert_to_ee.md +++ b/doc/update/package/convert_to_ee.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To convert an existing GitLab Community Edition (CE) server installed using the Omnibus GitLab packages to GitLab [Enterprise Edition](https://about.gitlab.com/pricing/) (EE), you install the EE diff --git a/doc/update/package/downgrade.md b/doc/update/package/downgrade.md index eff85ac9709..40e86020b24 100644 --- a/doc/update/package/downgrade.md +++ b/doc/update/package/downgrade.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This section contains general information on how to revert to an earlier version of a package. diff --git a/doc/update/package/index.md b/doc/update/package/index.md index 9994c17a87d..9d97450e0c4 100644 --- a/doc/update/package/index.md +++ b/doc/update/package/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can upgrade GitLab to a new version by using the GitLab package. diff --git a/doc/update/package/package_troubleshooting.md b/doc/update/package/package_troubleshooting.md index 1a1ee330ea2..aa24d7823a2 100644 --- a/doc/update/package/package_troubleshooting.md +++ b/doc/update/package/package_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Get the status of a GitLab installation diff --git a/doc/update/patch_versions.md b/doc/update/patch_versions.md index 767511e9720..72ab4bd30fe 100644 --- a/doc/update/patch_versions.md +++ b/doc/update/patch_versions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Select Version to Install @@ -107,7 +107,7 @@ sudo -u git -H make DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow the [install instruction](../integration/advanced_search/elasticsearch.md#install-elasticsearch). diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index a48532da4ac..2a971c8ca0d 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document serves as a guide to create a strong plan to upgrade a self-managed GitLab instance. diff --git a/doc/update/upgrading_from_ce_to_ee.md b/doc/update/upgrading_from_ce_to_ee.md index fe248c05d54..e7cdb5de9c7 100644 --- a/doc/update/upgrading_from_ce_to_ee.md +++ b/doc/update/upgrading_from_ce_to_ee.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: In the past we used separate documents for upgrading from @@ -86,7 +86,7 @@ sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow the [install instruction](../integration/advanced_search/elasticsearch.md#install-elasticsearch). diff --git a/doc/update/upgrading_from_source.md b/doc/update/upgrading_from_source.md index c8df168493e..51d2f88d0ba 100644 --- a/doc/update/upgrading_from_source.md +++ b/doc/update/upgrading_from_source.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Make sure you view this upgrade guide from the branch (version) of GitLab you would like to install (for example, `16.0`). You can select the required version of documentation in the dropdown list in the upper-right corner of GitLab documentation page. diff --git a/doc/update/versions/gitlab_14_changes.md b/doc/update/versions/gitlab_14_changes.md index 07434ce85f9..b7c304f2ba2 100644 --- a/doc/update/versions/gitlab_14_changes.md +++ b/doc/update/versions/gitlab_14_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 14. Ensure you review these instructions for: @@ -118,7 +118,7 @@ For more information about upgrading GitLab Helm Chart, see [the release notes f DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - **Do not** upgrade to GitLab 14.9.0. Instead, use 14.9.1 or later. @@ -215,7 +215,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - LFS objects import and mirror issue in GitLab 14.6.0 to 14.7.2. When Geo is enabled, LFS objects fail to be saved for imported or mirrored projects. @@ -241,7 +241,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - LFS objects import and mirror issue in GitLab 14.6.0 to 14.7.2. When Geo is enabled, LFS objects fail to be saved for imported or mirrored projects. @@ -329,7 +329,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -358,7 +358,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.4.0 through 14.4.2](#1440) that can affect Geo and other features that rely on cronjobs. We recommend upgrading to GitLab 14.4.3 or later. @@ -413,7 +413,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -584,7 +584,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -689,7 +689,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -772,7 +772,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We found an [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/336013) where the container registry replication wasn't fully working if you used multi-arch images. In case of a multi-arch image, only the primary architecture @@ -933,7 +933,7 @@ Other issues: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We found an issue where [Primary sites cannot be removed from the UI](https://gitlab.com/gitlab-org/gitlab/-/issues/338231). diff --git a/doc/update/versions/gitlab_15_changes.md b/doc/update/versions/gitlab_15_changes.md index 94295365db0..564b1d7c988 100644 --- a/doc/update/versions/gitlab_15_changes.md +++ b/doc/update/versions/gitlab_15_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 15. Ensure you review these instructions for: @@ -44,7 +44,7 @@ see [Packaged PostgreSQL deployed in an HA/Geo Cluster](https://docs.gitlab.com/ DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - Some project imports do not initialize wiki repositories on project creation. See [the details and workaround](gitlab_16_changes.md#wiki-repositories-not-initialized-on-project-creation). @@ -144,7 +144,7 @@ if you can't upgrade to 15.11.12 and later. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -194,7 +194,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -206,7 +206,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -220,7 +220,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -235,7 +235,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -252,7 +252,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -266,7 +266,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -280,7 +280,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -294,7 +294,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -308,7 +308,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the upgrades. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -323,7 +323,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -385,7 +385,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -402,7 +402,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -416,7 +416,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -429,7 +429,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -443,7 +443,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6, and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -457,7 +457,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -471,7 +471,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -485,7 +485,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -524,7 +524,7 @@ potentially cause downtime. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -595,7 +595,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -674,7 +674,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -749,7 +749,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -826,7 +826,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -870,7 +870,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Geo proxying](../../administration/geo/secondary_proxy/index.md) was [enabled by default for different URLs](https://gitlab.com/gitlab-org/gitlab/-/issues/346112) in 15.1. This may be a breaking change. If needed, you may [disable Geo proxying](../../administration/geo/secondary_proxy/index.md#disable-geo-proxying). If you are using SAML with different URLs, you must modify your SAML configuration and your Identity Provider configuration. For more information, see the [Geo with Single Sign-On (SSO) documentation](../../administration/geo/replication/single_sign_on.md). - LFS transfers can redirect to the primary from secondary site mid-session. See @@ -1053,7 +1053,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - Incorrect object storage LFS files deletion on Geo secondary sites. See [the details and workaround](#incorrect-object-storage-lfs-file-deletion-on-secondary-sites). diff --git a/doc/update/versions/gitlab_16_changes.md b/doc/update/versions/gitlab_16_changes.md index 58411f6d4ee..680858ba36f 100644 --- a/doc/update/versions/gitlab_16_changes.md +++ b/doc/update/versions/gitlab_16_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 16. Ensure you review these instructions for: @@ -702,7 +702,7 @@ Workaround: A possible workaround is to [disable proxying](../../administration/ DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Specific information applies to installations using Geo: @@ -784,7 +784,7 @@ Specific information applies to Linux package installations: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Specific information applies to installations using Geo: diff --git a/doc/update/with_downtime.md b/doc/update/with_downtime.md index 8e290972246..7d4a216050f 100644 --- a/doc/update/with_downtime.md +++ b/doc/update/with_downtime.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed While you can upgrade a multi-node GitLab deployment [with zero downtime](zero_downtime.md), there are a number of constraints. In particular, you can upgrade to only one minor release @@ -197,7 +197,7 @@ Upgrade a standalone Redis server by [upgrading the GitLab package](package/inde DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow [the zero downtime instructions](zero_downtime.md#redis-ha-using-sentinel) for upgrading your Redis HA cluster. diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md index 7a9d726cc90..c33b78cd1c4 100644 --- a/doc/update/zero_downtime.md +++ b/doc/update/zero_downtime.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed It's possible to upgrade to a newer major, minor, or patch version of GitLab without having to take your GitLab instance offline. However, for this to work @@ -333,7 +333,7 @@ setting `gitlab_rails['auto_migrate'] = false` in DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Package upgrades may involve version updates to the bundled Redis service. On instances using [Redis for scaling](../administration/redis/index.md), @@ -436,7 +436,7 @@ procedure. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: You can only upgrade one minor release at a time. @@ -557,7 +557,7 @@ setting `gitlab_rails['auto_migrate'] = false` in DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: You can only upgrade one minor release at a time. You also must first start with the Gitaly cluster, updating Gitaly one node one at a time. This will ensure access to the Git repositories for the remainder of the upgrade process. diff --git a/doc/user/ai_features.md b/doc/user/ai_features.md index 7ff6f09faee..d70a6bf6146 100644 --- a/doc/user/ai_features.md +++ b/doc/user/ai_features.md @@ -36,22 +36,27 @@ Some features are still in development. View details about [support for each sta ## Enable AI/ML features -- Experiment and Beta features - - All features categorized as - [Experiment features](../policy/experiment-beta-support.md#experiment) or - [Beta features](../policy/experiment-beta-support.md#beta) - require that this setting is enabled at the group level. - - Their usage is subject to the - [Testing Terms of Use](https://handbook.gitlab.com/handbook/legal/testing-agreement/). - - Experiment and Beta features are disabled by default. - - This setting is available to Ultimate groups on SaaS and can be set by a user - who has the Owner role in the group. - - View [how to enable this setting](group/manage.md#enable-experiment-and-beta-features). +For features listed as Experiment and Beta: + +- These features are disabled by default. +- To enable, a user with the Owner role for the group must [turn on this setting](group/manage.md#enable-experiment-and-beta-features). + On GitLab.com, this setting is available for Ultimate subscriptions only. +- These features are subject to the + [Testing Terms of Use](https://handbook.gitlab.com/handbook/legal/testing-agreement/). + +For all self-managed features: + +- Your firewalls and HTTP proxy servers must allow outbound connections + to `cloud.gitlab.com`. To use an HTTP proxy, both `gitLab _workhorse` and `gitLab_rails` must have the necessary + [web proxy environment variables](https://docs.gitlab.com/omnibus/settings/environment-variables.html) set. + +For other features: + - [Code Suggestions](project/repository/code_suggestions/index.md) is enabled when you purchase the GitLab Duo Pro add-on and assign seats to users. - [Chat](gitlab_duo_chat.md) - View [how to enable for self-managed](gitlab_duo_chat.md#for-self-managed-users). - - View [how to enable for SaaS](gitlab_duo_chat.md#for-saas-users). + - View [how to enable for GitLab.com](gitlab_duo_chat.md#for-saas-users). ## Experimental AI features and how to use them diff --git a/doc/user/gitlab_duo_chat.md b/doc/user/gitlab_duo_chat.md index b84217132cf..60ce79c3595 100644 --- a/doc/user/gitlab_duo_chat.md +++ b/doc/user/gitlab_duo_chat.md @@ -181,8 +181,12 @@ Learn about [data usage when using GitLab Duo Chat](ai_features.md#data-usage). Prerequisites: -- You are using GitLab version 16.8 or later. +- You have GitLab version 16.8 or later. - The Premium or Ultimate license is activated in your GitLab instance by using [cloud licensing](https://about.gitlab.com/pricing/licensing-faq/cloud-licensing/). +- Your firewalls and HTTP proxy servers allow outbound connections + to `cloud.gitlab.com`. To use an HTTP proxy, both + `gitLab _workhorse` and `gitLab_rails` have the necessary + [web proxy environment variables](https://docs.gitlab.com/omnibus/settings/environment-variables.html) set. - All of the users in your instance have the latest version of their IDE extension. - You are an administrator. diff --git a/doc/user/project/service_desk/configure.md b/doc/user/project/service_desk/configure.md index a6518339421..6e374db45b1 100644 --- a/doc/user/project/service_desk/configure.md +++ b/doc/user/project/service_desk/configure.md @@ -105,7 +105,7 @@ To keep your emails on brand, you can create a custom new note email template. T DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/344819) in GitLab 15.9. @@ -458,7 +458,7 @@ In GitLab: DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2201) in GitLab 13.0. > - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/284656) in GitLab 13.8. diff --git a/lib/gitlab/cycle_analytics/summary/issue.rb b/lib/gitlab/cycle_analytics/summary/issue.rb index ed6c985009c..559466ea86c 100644 --- a/lib/gitlab/cycle_analytics/summary/issue.rb +++ b/lib/gitlab/cycle_analytics/summary/issue.rb @@ -15,7 +15,7 @@ module Gitlab end def title - n_('New Issue', 'New Issues', value.to_i) + n_('New issue', 'New issues', value.to_i) end def value diff --git a/locale/gitlab.pot b/locale/gitlab.pot index 2d479c13720..94f5042af9a 100644 --- a/locale/gitlab.pot +++ b/locale/gitlab.pot @@ -532,6 +532,9 @@ msgstr "" msgid "%{address} is an invalid IP address range" msgstr "" +msgid "%{argument_name} must be formatted correctly. For example: 1h 30m." +msgstr "" + msgid "%{author_link} cloned %{original_issue} to %{new_issue}." msgstr "" @@ -15291,7 +15294,7 @@ msgstr "" msgid "Customize your pipeline configuration." msgstr "" -msgid "Cycle Time" +msgid "Cycle time" msgstr "" msgid "CycleAnalyticsEvent|%{label_reference} label was added to the issue" @@ -23802,6 +23805,9 @@ msgstr "" msgid "GroupPage|Group ID: %{id}" msgstr "" +msgid "GroupPage|Group settings" +msgstr "" + msgid "GroupRoadmap|%{dateWord} – No end date" msgstr "" @@ -29030,9 +29036,6 @@ msgstr "" msgid "Layout|Fluid" msgstr "" -msgid "Lead Time" -msgstr "" - msgid "Lead Time for Changes" msgstr "" @@ -32594,9 +32597,7 @@ msgid "New Identity" msgstr "" msgid "New Issue" -msgid_plural "New Issues" -msgstr[0] "" -msgstr[1] "" +msgstr "" msgid "New Jira import" msgstr "" @@ -32695,7 +32696,9 @@ msgid "New incident has been created" msgstr "" msgid "New issue" -msgstr "" +msgid_plural "New issues" +msgstr[0] "" +msgstr[1] "" msgid "New issue title" msgstr "" @@ -33931,6 +33934,9 @@ msgstr "" msgid "ObservabilityLogs|Warning" msgstr "" +msgid "ObservabilityMetrics|Attributes" +msgstr "" + msgid "ObservabilityMetrics|Cancel" msgstr "" @@ -33976,24 +33982,24 @@ msgstr "" msgid "ObservabilityMetrics|Select attributes" msgstr "" +msgid "ObservabilityMetrics|Select function" +msgstr "" + +msgid "ObservabilityMetrics|Selected attributes" +msgstr "" + msgid "ObservabilityMetrics|Type" msgstr "" msgid "ObservabilityMetrics|Value" msgstr "" -msgid "ObservabilityMetrics|all" -msgstr "" - msgid "ObservabilityMetrics|is like" msgstr "" msgid "ObservabilityMetrics|is not like" msgstr "" -msgid "ObservabilityMetrics|multiple" -msgstr "" - msgid "Observability|Enable" msgstr "" diff --git a/spec/dot_gitlab_ci/rules_spec.rb b/spec/dot_gitlab_ci/rules_spec.rb index 765929b1df4..21f03126510 100644 --- a/spec/dot_gitlab_ci/rules_spec.rb +++ b/spec/dot_gitlab_ci/rules_spec.rb @@ -26,6 +26,31 @@ RSpec.describe '.gitlab/ci/rules.gitlab-ci.yml', feature_category: :tooling do end end + describe '.qa:rules:manual-omnibus-and-follow-up-e2e' do + let(:base_rules) { config.dig('.qa:rules:manual-omnibus-and-follow-up-e2e', 'rules') } + + context 'with .qa:rules:follow-up-e2e' do + let(:derived_rules) { config.dig('.qa:rules:follow-up-e2e', 'rules') } + + it 'has the same rules as the base, but with manual jobs changed to automatic' do + base_rules.zip(derived_rules).each do |(base, derived)| + # Exception: + # + # - !reference [".qa:rules:code-merge-request-manual", rules] becomes + # - !reference [".qa:rules:code-merge-request-allowed-to-fail", rules] + # + # This is because we want the rules to be automatic, but still allowed to fail + if base.is_a?(Array) && base.first == '.qa:rules:code-merge-request-manual' + expect(derived.first).to eq('.qa:rules:code-merge-request-allowed-to-fail') + next + end + + expect(derived).to eq(base) + end + end + end + end + describe 'start-as-if-foss' do let(:base_rules) { config.dig('.as-if-foss:rules:start-as-if-foss', 'rules') } diff --git a/spec/features/cycle_analytics_spec.rb b/spec/features/cycle_analytics_spec.rb index ff2ab690a50..4dabeb14898 100644 --- a/spec/features/cycle_analytics_spec.rb +++ b/spec/features/cycle_analytics_spec.rb @@ -99,7 +99,7 @@ RSpec.describe 'Value Stream Analytics', :js, feature_category: :value_stream_ma aggregate_failures 'with relevant values' do expect(metrics_tiles).to have_content('Commit') expect(metrics_tiles).to have_content('Deploy') - expect(metrics_tiles).to have_content('New Issue') + expect(metrics_tiles).to have_content('New issue') end end diff --git a/spec/finders/groups_finder_spec.rb b/spec/finders/groups_finder_spec.rb index b9add5b7db2..c1ca19e29ec 100644 --- a/spec/finders/groups_finder_spec.rb +++ b/spec/finders/groups_finder_spec.rb @@ -180,17 +180,29 @@ RSpec.describe GroupsFinder, feature_category: :groups_and_projects do let_it_be(:internal_sub_subgroup) { create(:group, :internal, parent: public_subgroup) } let_it_be(:private_sub_subgroup) { create(:group, :private, parent: public_subgroup) } let_it_be(:public_sub_subgroup) { create(:group, :public, parent: public_subgroup) } + let_it_be(:invited_to_group) { create(:group, :public) } + let_it_be(:invited_to_subgroup) { create(:group, :public) } let(:params) { { include_parent_descendants: true, parent: parent_group } } + before do + parent_group.shared_with_groups << invited_to_group + public_subgroup.shared_with_groups << invited_to_subgroup + end + context 'with nil parent' do - it 'returns all accessible groups' do + before do params[:parent] = nil + end + + it 'returns all accessible groups' do expect(described_class.new(user, params).execute).to contain_exactly( parent_group, public_subgroup, internal_sub_subgroup, - public_sub_subgroup + public_sub_subgroup, + invited_to_group, + invited_to_subgroup ) end end @@ -227,6 +239,22 @@ RSpec.describe GroupsFinder, feature_category: :groups_and_projects do private_sub_subgroup ) end + + context 'when include shared groups is set' do + before do + params[:include_parent_shared_groups] = true + end + + it 'returns all group descendants with shared groups' do + expect(described_class.new(user, params).execute).to contain_exactly( + public_subgroup, + public_sub_subgroup, + internal_sub_subgroup, + private_sub_subgroup, + invited_to_group + ) + end + end end end diff --git a/spec/frontend/analytics/cycle_analytics/components/value_stream_metrics_spec.js b/spec/frontend/analytics/cycle_analytics/components/value_stream_metrics_spec.js index e1e955cec2c..a78ccf81522 100644 --- a/spec/frontend/analytics/cycle_analytics/components/value_stream_metrics_spec.js +++ b/spec/frontend/analytics/cycle_analytics/components/value_stream_metrics_spec.js @@ -95,7 +95,7 @@ describe('ValueStreamMetrics', () => { it('with a filter function, will call the function with the metrics data', async () => { const filteredData = [ - { identifier: 'issues', value: '3', title: 'New Issues', description: 'foo' }, + { identifier: 'issues', value: '3', title: 'New issues', description: 'foo' }, ]; mockFilterFn = jest.fn(() => filteredData); diff --git a/spec/frontend/analytics/cycle_analytics/mock_data.js b/spec/frontend/analytics/cycle_analytics/mock_data.js index 73387606433..aa0706ddf7b 100644 --- a/spec/frontend/analytics/cycle_analytics/mock_data.js +++ b/spec/frontend/analytics/cycle_analytics/mock_data.js @@ -37,7 +37,7 @@ const stageFixtures = { }; export const summary = [ - { value: '20', title: 'New Issues' }, + { value: '20', title: 'New issues' }, { value: null, title: 'Commits' }, { value: null, title: 'Deploys' }, { value: null, title: 'Deployment Frequency', unit: '/day' }, @@ -109,7 +109,7 @@ export const selectedStage = { export const convertedData = { summary: [ - { value: '20', title: 'New Issues' }, + { value: '20', title: 'New issues' }, { value: '-', title: 'Commits' }, { value: '-', title: 'Deploys' }, { value: '-', title: 'Deployment Frequency', unit: '/day' }, diff --git a/spec/frontend/analytics/shared/utils_spec.js b/spec/frontend/analytics/shared/utils_spec.js index 24af7b836d5..1039372336e 100644 --- a/spec/frontend/analytics/shared/utils_spec.js +++ b/spec/frontend/analytics/shared/utils_spec.js @@ -203,7 +203,7 @@ describe('prepareTimeMetricsData', () => { }); it('will add a `label` key', () => { - expect(prepared).toMatchObject([{ label: 'New Issues' }, { label: 'Commits' }]); + expect(prepared).toMatchObject([{ label: 'New issues' }, { label: 'Commits' }]); }); it('will add a popover description using the key if it is provided', () => { diff --git a/spec/frontend/groups_projects/components/more_actions_dropdown_spec.js b/spec/frontend/groups_projects/components/more_actions_dropdown_spec.js index 3595038c03d..0ba0e518ac1 100644 --- a/spec/frontend/groups_projects/components/more_actions_dropdown_spec.js +++ b/spec/frontend/groups_projects/components/more_actions_dropdown_spec.js @@ -19,6 +19,8 @@ describe('moreActionsDropdown', () => { withdrawPath: '', withdrawConfirmMessage: '', requestAccessPath: '', + canEdit: false, + editPath: '', ...provideData, }, propsData, @@ -33,6 +35,8 @@ describe('moreActionsDropdown', () => { findDropdown().vm.$emit('show'); }; const findDropdownGroup = () => wrapper.findComponent(GlDisclosureDropdownGroup); + const findGroupSettings = () => wrapper.findByTestId('settings-group-link'); + const findProjectSettings = () => wrapper.findByTestId('settings-project-link'); describe('copy id', () => { describe('project namespace type', () => { @@ -198,4 +202,67 @@ describe('moreActionsDropdown', () => { }); }); }); + + describe('settings', () => { + describe('when `canEdit` is `true`', () => { + const provideData = { + editPath: '/settings', + canEdit: true, + }; + + describe('when `isGroup` is set to `false`', () => { + beforeEach(() => { + createComponent({ + provideData, + }); + showDropdown(); + }); + + it('renders `Project settings` dropdown item', () => { + const settingsDropdownItem = findProjectSettings(); + + expect(settingsDropdownItem.text()).toBe('Project settings'); + expect(settingsDropdownItem.attributes('href')).toBe(provideData.editPath); + }); + }); + + describe('when `isGroup` is set to `true`', () => { + beforeEach(() => { + createComponent({ + provideData: { + ...provideData, + isGroup: true, + }, + }); + showDropdown(); + }); + + it('renders `Group settings` dropdown item', () => { + const settingsDropdownItem = findGroupSettings(); + + expect(settingsDropdownItem.text()).toBe('Group settings'); + expect(settingsDropdownItem.attributes('href')).toBe(provideData.editPath); + }); + }); + }); + + describe('when `canEdit` is `false`', () => { + const provideData = { + editPath: '/settings', + canEdit: false, + }; + + beforeEach(() => { + createComponent({ + provideData, + }); + showDropdown(); + }); + + it('does not render dropdown item', () => { + expect(findGroupSettings().exists()).toBe(false); + expect(findProjectSettings().exists()).toBe(false); + }); + }); + }); }); diff --git a/spec/frontend/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit_spec.js b/spec/frontend/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit_spec.js index 702c0ab1a6d..3278ef65718 100644 --- a/spec/frontend/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit_spec.js +++ b/spec/frontend/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit_spec.js @@ -2,6 +2,7 @@ import { GlForm, GlCollapsibleListbox, GlLoadingIcon } from '@gitlab/ui'; import { nextTick } from 'vue'; import { mountExtended } from 'helpers/vue_test_utils_helper'; import { __ } from '~/locale'; +import { groupIterationsResponse } from 'jest/work_items/mock_data'; import WorkItemSidebarDropdownWidgetWithEdit from '~/work_items/components/shared/work_item_sidebar_dropdown_widget_with_edit.vue'; describe('WorkItemSidebarDropdownWidgetWithEdit component', () => { @@ -26,12 +27,14 @@ describe('WorkItemSidebarDropdownWidgetWithEdit component', () => { multiSelect = false, infiniteScroll = false, infiniteScrollLoading = false, + clearSearchOnItemSelect = false, + listItems = [], } = {}) => { wrapper = mountExtended(WorkItemSidebarDropdownWidgetWithEdit, { propsData: { dropdownLabel: __('Iteration'), dropdownName: 'iteration', - listItems: [], + listItems, itemValue, canUpdate, updateInProgress, @@ -40,6 +43,7 @@ describe('WorkItemSidebarDropdownWidgetWithEdit component', () => { multiSelect, infiniteScroll, infiniteScrollLoading, + clearSearchOnItemSelect, }, slots, }); @@ -183,6 +187,24 @@ describe('WorkItemSidebarDropdownWidgetWithEdit component', () => { expect(findCollapsibleListbox().props('multiple')).toBe(true); }); + it('clears search on item select when props passes', async () => { + const listItems = groupIterationsResponse.data.workspace.attributes.nodes; + createComponent({ + isEditing: true, + clearSearchOnItemSelect: true, + listItems, + multiSelect: true, + }); + + await nextTick(); + + findCollapsibleListbox().vm.$emit('select', listItems[0].id); + + await nextTick(); + + expect(wrapper.emitted('searchStarted')).toEqual([[''], ['']]); + }); + it('supports infinite scrolling', async () => { createComponent({ isEditing: true, infiniteScroll: true }); diff --git a/spec/frontend/work_items/components/work_item_assignees_with_edit_spec.js b/spec/frontend/work_items/components/work_item_assignees_with_edit_spec.js index 110814db494..272ba3d3108 100644 --- a/spec/frontend/work_items/components/work_item_assignees_with_edit_spec.js +++ b/spec/frontend/work_items/components/work_item_assignees_with_edit_spec.js @@ -112,6 +112,12 @@ describe('WorkItemAssigneesWithEdit component', () => { expect(wrapper.emitted('error')).toEqual([[i18n.fetchError]]); }); + + it('passes the correct props to clear search text on item select', () => { + createComponent(); + + expect(findSidebarDropdownWidget().props('clearSearchOnItemSelect')).toBe(true); + }); }); describe('when assigning to current user', () => { diff --git a/spec/frontend/work_items/components/work_item_labels_with_edit_spec.js b/spec/frontend/work_items/components/work_item_labels_with_edit_spec.js index 25bbac20b39..bb4d4fc7cc5 100644 --- a/spec/frontend/work_items/components/work_item_labels_with_edit_spec.js +++ b/spec/frontend/work_items/components/work_item_labels_with_edit_spec.js @@ -141,7 +141,7 @@ describe('WorkItemLabelsWithEdit component', () => { dropdownName: 'label', updateInProgress: false, toggleDropdownText: 'No labels', - headerText: 'Select label', + headerText: 'Select labels', resetButtonLabel: 'Clear', multiSelect: true, itemValue: [], @@ -221,6 +221,12 @@ describe('WorkItemLabelsWithEdit component', () => { expect(wrapper.emitted('error')).toEqual([[I18N_WORK_ITEM_ERROR_FETCHING_LABELS]]); }); + it('passes the correct props to clear search text on item select', () => { + createComponent(); + + expect(findWorkItemSidebarDropdownWidget().props('clearSearchOnItemSelect')).toBe(true); + }); + it('update labels when labels are added', async () => { createComponent({ workItemQueryHandler: workItemQuerySuccess, diff --git a/spec/graphql/types/work_items/widget_interface_spec.rb b/spec/graphql/types/work_items/widget_interface_spec.rb index 6e66f335d89..1b5c88cd261 100644 --- a/spec/graphql/types/work_items/widget_interface_spec.rb +++ b/spec/graphql/types/work_items/widget_interface_spec.rb @@ -28,7 +28,7 @@ RSpec.describe Types::WorkItems::WidgetInterface, feature_category: :team_planni WorkItems::Widgets::StartAndDueDate | Types::WorkItems::Widgets::StartAndDueDateType WorkItems::Widgets::Milestone | Types::WorkItems::Widgets::MilestoneType WorkItems::Widgets::Participants | Types::WorkItems::Widgets::ParticipantsType - WorkItems::Widgets::TimeTracking | Types::WorkItems::Widgets::TimeTrackingType + WorkItems::Widgets::TimeTracking | Types::WorkItems::Widgets::TimeTracking::TimeTrackingType WorkItems::Widgets::Designs | Types::WorkItems::Widgets::DesignsType end diff --git a/spec/graphql/types/work_items/widgets/time_tracking/time_tracking_input_type_spec.rb b/spec/graphql/types/work_items/widgets/time_tracking/time_tracking_input_type_spec.rb new file mode 100644 index 00000000000..afdd3340d19 --- /dev/null +++ b/spec/graphql/types/work_items/widgets/time_tracking/time_tracking_input_type_spec.rb @@ -0,0 +1,9 @@ +# frozen_string_literal: true + +require 'spec_helper' + +RSpec.describe Types::WorkItems::Widgets::TimeTracking::TimeTrackingInputType, feature_category: :team_planning do + it { expect(described_class.graphql_name).to eq('WorkItemWidgetTimeTrackingInput') } + + it { expect(described_class.arguments.keys).to match_array(%w[timeEstimate timelog]) } +end diff --git a/spec/graphql/types/work_items/widgets/time_tracking_type_spec.rb b/spec/graphql/types/work_items/widgets/time_tracking/time_tracking_type_spec.rb similarity index 68% rename from spec/graphql/types/work_items/widgets/time_tracking_type_spec.rb rename to spec/graphql/types/work_items/widgets/time_tracking/time_tracking_type_spec.rb index 00b87517389..65e882a8f58 100644 --- a/spec/graphql/types/work_items/widgets/time_tracking_type_spec.rb +++ b/spec/graphql/types/work_items/widgets/time_tracking/time_tracking_type_spec.rb @@ -2,7 +2,7 @@ require 'spec_helper' -RSpec.describe Types::WorkItems::Widgets::TimeTrackingType, feature_category: :team_planning do +RSpec.describe Types::WorkItems::Widgets::TimeTracking::TimeTrackingType, feature_category: :team_planning do it 'exposes the expected fields' do expected_fields = %i[time_estimate total_time_spent timelogs type] diff --git a/spec/graphql/types/work_items/widgets/time_tracking/timelog_input_type_spec.rb b/spec/graphql/types/work_items/widgets/time_tracking/timelog_input_type_spec.rb new file mode 100644 index 00000000000..9e2cdeb2d19 --- /dev/null +++ b/spec/graphql/types/work_items/widgets/time_tracking/timelog_input_type_spec.rb @@ -0,0 +1,9 @@ +# frozen_string_literal: true + +require 'spec_helper' + +RSpec.describe Types::WorkItems::Widgets::TimeTracking::TimelogInputType, feature_category: :team_planning do + it { expect(described_class.graphql_name).to eq('WorkItemWidgetTimeTrackingTimelogInput') } + + it { expect(described_class.arguments.keys).to match_array(%w[timeSpent spentAt summary]) } +end diff --git a/spec/graphql/types/work_items/widgets/time_tracking/timelog_type_spec.rb b/spec/graphql/types/work_items/widgets/time_tracking/timelog_type_spec.rb new file mode 100644 index 00000000000..912a50c6bad --- /dev/null +++ b/spec/graphql/types/work_items/widgets/time_tracking/timelog_type_spec.rb @@ -0,0 +1,9 @@ +# frozen_string_literal: true + +require 'spec_helper' + +RSpec.describe Types::WorkItems::Widgets::TimeTracking::TimelogType, feature_category: :team_planning do + it { expect(described_class.graphql_name).to eq('WorkItemTimelog') } + + it { expect(described_class).to have_graphql_fields(%w[id spentAt timeSpent user note summary userPermissions]) } +end diff --git a/spec/lib/gitlab/cycle_analytics/stage_summary_spec.rb b/spec/lib/gitlab/cycle_analytics/stage_summary_spec.rb index f85fb1540d9..3746eece8fb 100644 --- a/spec/lib/gitlab/cycle_analytics/stage_summary_spec.rb +++ b/spec/lib/gitlab/cycle_analytics/stage_summary_spec.rb @@ -39,7 +39,7 @@ RSpec.describe Gitlab::CycleAnalytics::StageSummary, feature_category: :devops_r it 'returns the localized title' do Gitlab::I18n.with_locale(:ru) do - expect(subject[:title]).to eq(n_('New Issue', 'New Issues', 1)) + expect(subject[:title]).to eq(n_('New issue', 'New issues', 1)) end end end diff --git a/spec/lib/sidebars/projects/menus/hidden_menu_spec.rb b/spec/lib/sidebars/projects/menus/hidden_menu_spec.rb index a9e870934c4..292cc031edf 100644 --- a/spec/lib/sidebars/projects/menus/hidden_menu_spec.rb +++ b/spec/lib/sidebars/projects/menus/hidden_menu_spec.rb @@ -67,7 +67,7 @@ RSpec.describe Sidebars::Projects::Menus::HiddenMenu, feature_category: :navigat it_behaves_like 'access rights checks' end - describe 'New Issue' do + describe 'New issue' do let(:item_id) { :new_issue } it_behaves_like 'access rights checks' diff --git a/spec/models/concerns/ci/has_status_spec.rb b/spec/models/concerns/ci/has_status_spec.rb index 95f17c4f854..d1c92f886bf 100644 --- a/spec/models/concerns/ci/has_status_spec.rb +++ b/spec/models/concerns/ci/has_status_spec.rb @@ -296,18 +296,6 @@ RSpec.describe Ci::HasStatus, feature_category: :continuous_integration do end end - describe '.alive_or_scheduled' do - subject { CommitStatus.alive_or_scheduled } - - %i[running pending waiting_for_callback waiting_for_resource preparing created scheduled].each do |status| - it_behaves_like 'containing the job', status - end - - %i[failed success canceled skipped].each do |status| - it_behaves_like 'not containing the job', status - end - end - describe '.created_or_pending' do subject { CommitStatus.created_or_pending } diff --git a/spec/models/group_spec.rb b/spec/models/group_spec.rb index f9f18a8b23e..95c4af9c41c 100644 --- a/spec/models/group_spec.rb +++ b/spec/models/group_spec.rb @@ -1306,6 +1306,37 @@ RSpec.describe Group, feature_category: :groups_and_projects do it { is_expected.to match_array(groups) } end + + describe 'descendants_with_shared_with_groups' do + subject { described_class.descendants_with_shared_with_groups(parent_group) } + + let_it_be(:grand_parent_group) { create(:group, :public) } + let_it_be(:parent_group) { create(:group, :public, parent: grand_parent_group) } + let_it_be(:subgroup) { create(:group, :public, parent: parent_group) } + let_it_be(:subsubgroup) { create(:group, :public, parent: subgroup) } + + let_it_be(:shared_to_group) { create(:group, :public) } + let_it_be(:shared_to_sub_group) { create(:group, :public) } + + context 'when parent group is nil' do + let(:parent_group) { nil } + + it { is_expected.to match_array([]) } + end + + context 'when parent group is present and there are shared groups' do + before do + parent_group.shared_with_groups << shared_to_group + subgroup.shared_with_groups << shared_to_sub_group + end + + it { is_expected.to match_array([subgroup, subsubgroup, shared_to_group]) } + end + + context 'when parent group is present and there are no shared groups' do + it { is_expected.to match_array([subgroup, subsubgroup]) } + end + end end describe '#to_reference' do diff --git a/spec/requests/api/graphql/mutations/work_items/update_spec.rb b/spec/requests/api/graphql/mutations/work_items/update_spec.rb index 867c6fdfbb8..a01778c95e0 100644 --- a/spec/requests/api/graphql/mutations/work_items/update_spec.rb +++ b/spec/requests/api/graphql/mutations/work_items/update_spec.rb @@ -1596,7 +1596,17 @@ RSpec.describe 'Update a work item', feature_category: :team_planning do end end - context 'with time tracking widget input' do + context 'with time tracking widget input', time_travel_to: "2024-02-20" do + shared_examples 'request with error' do |message| + it 'ignores update and returns an error' do + post_graphql_mutation(mutation, current_user: current_user) + + expect(response).to have_gitlab_http_status(:success) + expect(mutation_response['workItem']).to be_nil + expect(mutation_response['errors'].first).to include(message) + end + end + shared_examples 'mutation updating work item with time tracking data' do it 'updates time tracking' do expect do @@ -1607,12 +1617,15 @@ RSpec.describe 'Update a work item', feature_category: :team_planning do ) expect(mutation_response['workItem']['widgets']).to include( - 'timeEstimate' => 12.hours.to_i, - 'totalTimeSpent' => 2.hours.to_i, + 'timeEstimate' => expected_result[:time_estimate], + 'totalTimeSpent' => expected_result[:time_spent], 'timelogs' => { 'nodes' => [ { - 'timeSpent' => 2.hours.to_i + 'timeSpent' => expected_result[:time_spent], + 'spentAt' => expected_result[:spent_at], + 'summary' => expected_result[:summary], + 'user' => { "username" => current_user.username } } ] }, @@ -1620,7 +1633,7 @@ RSpec.describe 'Update a work item', feature_category: :team_planning do ) expect(mutation_response['workItem']['widgets']).to include( - 'description' => 'some description', + 'description' => expected_result[:description], 'type' => 'DESCRIPTION' ) end @@ -1637,6 +1650,11 @@ RSpec.describe 'Update a work item', feature_category: :team_planning do timelogs { nodes { timeSpent + spentAt + summary + user { + username + } } } } @@ -1650,46 +1668,118 @@ RSpec.describe 'Update a work item', feature_category: :team_planning do FIELDS end - let_it_be(:group_work_item) { create(:work_item, :task, :group_level, namespace: group) } + let_it_be_with_reload(:group_work_item) { create(:work_item, :task, :group_level, namespace: group) } context 'when adding time estimate and time spent' do - context 'with quick action' do - let(:input) { { 'descriptionWidget' => { 'description' => "some description\n\n/estimate 12h\n/spend 2h" } } } + context 'when mutating the work item' do + let(:spent_at) { 2.days.ago.to_date } + let(:summary) { "doing testing" } + let(:input) do + { + 'timeTrackingWidget' => { + 'timeEstimate' => "12h", + 'timelog' => { + 'timeSpent' => "2h", + 'spentAt' => spent_at.strftime("%F"), + 'summary' => "doing testing" + } + } + } + end - it_behaves_like 'mutation updating work item with time tracking data' + let(:expected_result) do + { + time_estimate: 12.hours.to_i, + time_spent: 2.hours.to_i, + spent_at: spent_at.to_time.utc.strftime("%FT%TZ"), + summary: summary, + description: nil + } + end + + context 'when work item belongs to a project' do + it_behaves_like 'mutation updating work item with time tracking data' + end + + context 'when work item belongs to a group' do + let(:mutation_work_item) { group_work_item } + + it_behaves_like 'mutation updating work item with time tracking data' + end + + context 'when time estimate format is invalid' do + let(:input) { { 'timeTrackingWidget' => { 'timeEstimate' => "12abc" } } } + + it_behaves_like 'request with error', 'Time estimate must be formatted correctly. For example: 1h 30m.' + end + + context 'when time spent format is invalid' do + let(:input) { { 'timeTrackingWidget' => { 'timelog' => { 'timeSpent' => "2abc" } } } } + + it_behaves_like 'request with error', 'Time spent must be formatted correctly. For example: 1h 30m.' + end end - context 'when work item belongs to the group' do - let(:mutation_work_item) { group_work_item } + context 'with quick action' do let(:input) { { 'descriptionWidget' => { 'description' => "some description\n\n/estimate 12h\n/spend 2h" } } } + let(:spent_at) { Date.current } + let(:expected_result) do + { + time_estimate: 12.hours.to_i, + time_spent: 2.hours.to_i, + spent_at: spent_at.strftime("%FT%TZ"), + summary: nil, + description: "some description" + } + end - it_behaves_like 'mutation updating work item with time tracking data' + context 'when work item belongs to a project' do + it_behaves_like 'mutation updating work item with time tracking data' + end + + context 'when work item belongs to a group' do + let(:mutation_work_item) { group_work_item } + + it_behaves_like 'mutation updating work item with time tracking data' + end end end context 'when the work item type does not support time tracking widget' do - let_it_be(:work_item) { create(:work_item, :task, project: project) } + context 'with quick action' do + let_it_be(:work_item) { create(:work_item, :task, project: project) } - let(:input) { { 'descriptionWidget' => { 'description' => "some description\n\n/estimate 12h\n/spend 2h" } } } + let(:spent_at) { Date.current } + let(:input) { { 'descriptionWidget' => { 'description' => "some description\n\n/estimate 12h\n/spend 2h" } } } + let(:expected_result) do + { + time_estimate: 12.hours.to_i, + time_spent: 2.hours.to_i, + spent_at: spent_at.strftime("%FT%TZ"), + summary: nil, + description: "some description" + } + end - before do - WorkItems::Type.default_by_type(:task).widget_definitions - .find_by_widget_type(:time_tracking).update!(disabled: true) - end + before do + WorkItems::Type.default_by_type(:task).widget_definitions + .find_by_widget_type(:time_tracking).update!(disabled: true) + end - it 'ignores the quick action' do - expect do - post_graphql_mutation(mutation, current_user: current_user) - work_item.reload - end.not_to change { work_item.time_estimate } + it 'ignores the quick action' do + expect do + post_graphql_mutation(mutation, current_user: current_user) + work_item.reload + end.not_to change { work_item.time_estimate } - expect(mutation_response['workItem']['widgets']).to include( - 'description' => "some description", - 'type' => 'DESCRIPTION' - ) - expect(mutation_response['workItem']['widgets']).not_to include( - 'type' => 'TIME_TRACKING' - ) + expect(mutation_response['workItem']['widgets']).to include( + 'description' => "some description", + 'type' => 'DESCRIPTION' + ) + expect(mutation_response['workItem']['widgets']).not_to include( + 'type' => 'TIME_TRACKING' + ) + end end end end diff --git a/spec/requests/api/issues/post_projects_issues_spec.rb b/spec/requests/api/issues/post_projects_issues_spec.rb index b9304cb1342..b2b330d81ef 100644 --- a/spec/requests/api/issues/post_projects_issues_spec.rb +++ b/spec/requests/api/issues/post_projects_issues_spec.rb @@ -290,7 +290,7 @@ RSpec.describe API::Issues, :aggregate_failures, feature_category: :team_plannin before do post api("/projects/#{project.id}/issues", user), params: { - title: 'New Issue', + title: 'New issue', merge_request_to_resolve_discussions_of: merge_request.iid } end @@ -302,7 +302,7 @@ RSpec.describe API::Issues, :aggregate_failures, feature_category: :team_plannin before do post api("/projects/#{project.id}/issues", user), params: { - title: 'New Issue', + title: 'New issue', merge_request_to_resolve_discussions_of: merge_request.iid, discussion_to_resolve: discussion.id } diff --git a/spec/services/work_items/callbacks/time_tracking_spec.rb b/spec/services/work_items/callbacks/time_tracking_spec.rb index bd3fe09b887..546448afb1a 100644 --- a/spec/services/work_items/callbacks/time_tracking_spec.rb +++ b/spec/services/work_items/callbacks/time_tracking_spec.rb @@ -14,7 +14,7 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann end let(:current_user) { reporter } - let(:params) do + let(:non_string_params) do { time_estimate: 12.hours.to_i, spend_time: { @@ -25,9 +25,23 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann } end + let(:string_params) do + { + time_estimate: "12h", + timelog: { + time_spent: "2h", + summary: "some summary" + } + } + end + let(:callback) { described_class.new(issuable: issuable, current_user: current_user, params: params) } describe '#after_initialize' do + shared_examples 'raises a WidgetError' do + it { expect { subject }.to raise_error(::WorkItems::Widgets::BaseService::WidgetError, message) } + end + shared_examples 'sets work item time tracking data' do it 'correctly sets time tracking data', :aggregate_failures do callback.after_initialize @@ -60,7 +74,17 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann context 'and work item is not persisted' do let(:project_work_item) { build(:work_item, :incident, project: project) } - it_behaves_like 'sets work item time tracking data' + context 'with non string params' do + let(:params) { non_string_params } + + it_behaves_like 'sets work item time tracking data' + end + + context 'with string params' do + let(:params) { string_params } + + it_behaves_like 'sets work item time tracking data' + end context 'when time tracking param is not present' do let(:params) { {} } @@ -69,6 +93,8 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann end context 'when widget does not exist in new type' do + let(:params) { non_string_params } + before do allow(callback).to receive(:excluded_in_new_type?).and_return(true) end @@ -84,7 +110,35 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann let_it_be(:timelog) { create(:timelog, issue: project_work_item, time_spent: 3.hours.to_i) } - it_behaves_like 'sets work item time tracking data' + context 'with non string params' do + let(:params) { non_string_params } + + it_behaves_like 'sets work item time tracking data' + end + + context 'with string params' do + let(:params) { string_params } + + it_behaves_like 'sets work item time tracking data' + end + + context 'when resetting time spent' do + let(:params) do + { + timelog: { + time_spent: ":reset", + summary: "remove spent data" + } + } + end + + it 'resets timelogs' do + callback.after_initialize + + # latest timelog entry is not persisted yet so we cannot use total_time_spent + expect(issuable.timelogs.sum(&:time_spent)).to eq(0) + end + end context 'when time tracking param is not present' do let(:params) { {} } @@ -93,6 +147,8 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann end context 'when widget does not exist in new type' do + let(:params) { string_params } + before do allow(callback).to receive(:excluded_in_new_type?).and_return(true) end @@ -108,7 +164,17 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann context 'and work item is not persisted' do let(:group_work_item) { build(:work_item, :task, :group_level, namespace: group) } - it_behaves_like 'sets work item time tracking data' + context 'with non string params' do + let(:params) { non_string_params } + + it_behaves_like 'sets work item time tracking data' + end + + context 'with string params' do + let(:params) { string_params } + + it_behaves_like 'sets work item time tracking data' + end context 'when time tracking param is not present' do let(:params) { {} } @@ -124,7 +190,39 @@ RSpec.describe WorkItems::Callbacks::TimeTracking, feature_category: :team_plann let_it_be(:timelog) { create(:timelog, issue: group_work_item, time_spent: 3.hours.to_i) } - it_behaves_like 'sets work item time tracking data' + context 'with non string params' do + let(:params) { non_string_params } + + it_behaves_like 'sets work item time tracking data' + end + + context 'with string params' do + let(:params) { string_params } + + it_behaves_like 'sets work item time tracking data' + end + end + end + + context 'with invalid data' do + let_it_be(:issuable) { create(:work_item, :task, project: project, time_estimate: 2.hours.to_i) } + + subject(:after_initialize) { callback.after_initialize } + + context 'when time_estimate is invalid' do + let(:params) { { time_estimate: "12abc" } } + + it_behaves_like 'raises a WidgetError' do + let(:message) { 'Time estimate must be formatted correctly. For example: 1h 30m.' } + end + end + + context 'when time_spent is invalid' do + let(:params) { { timelog: { time_spent: "2abc" } } } + + it_behaves_like 'raises a WidgetError' do + let(:message) { 'Time spent must be formatted correctly. For example: 1h 30m.' } + end end end end diff --git a/spec/support/shared_examples/analytics/cycle_analytics/flow_metrics_examples.rb b/spec/support/shared_examples/analytics/cycle_analytics/flow_metrics_examples.rb index b436fa18a9a..fb82e1b0820 100644 --- a/spec/support/shared_examples/analytics/cycle_analytics/flow_metrics_examples.rb +++ b/spec/support/shared_examples/analytics/cycle_analytics/flow_metrics_examples.rb @@ -98,7 +98,7 @@ RSpec.shared_examples 'value stream analytics flow metrics issueCount examples' 'identifier' => 'issues', 'unit' => nil, 'value' => 4, - 'title' => n_('New Issue', 'New Issues', 4) + 'title' => n_('New issue', 'New issues', 4) }) end @@ -118,7 +118,7 @@ RSpec.shared_examples 'value stream analytics flow metrics issueCount examples' 'identifier' => 'issues', 'unit' => nil, 'value' => 2, - 'title' => n_('New Issue', 'New Issues', 2) + 'title' => n_('New issue', 'New issues', 2) }) end end @@ -141,7 +141,7 @@ RSpec.shared_examples 'value stream analytics flow metrics issueCount examples' 'identifier' => 'issues', 'unit' => nil, 'value' => 1, - 'title' => n_('New Issue', 'New Issues', 1) + 'title' => n_('New issue', 'New issues', 1) }) end end