Commit 5427b269 authored by Marcia Ramos's avatar Marcia Ramos

add "premium" badges

parent 21413c6d
# Auditor users # Auditor users **[PREMIUM ONLY]**
>[Introduced][ee-998] in [GitLab Premium][eep] 8.17. >[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
......
# LDAP Additions in GitLab EE # LDAP Additions in GitLab EE **[STARTER ONLY]**
This is a continuation of the main [LDAP documentation](ldap.md), detailing LDAP This is a continuation of the main [LDAP documentation](ldap.md), detailing LDAP
features specific to GitLab Enterprise Edition. features specific to GitLab Enterprise Edition.
...@@ -47,7 +47,7 @@ The process will also update the following user information: ...@@ -47,7 +47,7 @@ The process will also update the following user information:
> **Note:** The LDAP sync process updates existing users while new users will > **Note:** The LDAP sync process updates existing users while new users will
be created on first sign in. be created on first sign in.
## Group Sync ## Group Sync **[PREMIUM ONLY]**
If your LDAP supports the `memberof` property, GitLab will add the user to any If your LDAP supports the `memberof` property, GitLab will add the user to any
new groups they might be added to when the user logs in. That way they don't need new groups they might be added to when the user logs in. That way they don't need
......
# Database Load Balancing # Database Load Balancing **[PREMIUM ONLY]**
> [Introduced][ee-1283] in [GitLab Premium][eep] 9.0. > [Introduced][ee-1283] in [GitLab Premium][eep] 9.0.
......
# Geo (Geo Replication) # Geo (Geo Replication) **[PREMIUM]**
> **Notes:** > **Notes:**
- Geo is part of [GitLab Premium][ee]. - Geo is part of [GitLab Premium][ee].
......
# Working with the bundled Consul service # Working with the bundled Consul service **[PREMIUM ONLY]**
## Overview ## Overview
......
...@@ -91,8 +91,6 @@ _The artifacts are stored by default in ...@@ -91,8 +91,6 @@ _The artifacts are stored by default in
- [Introduced][ee-1762] in [GitLab Premium][eep] 9.4. - [Introduced][ee-1762] in [GitLab Premium][eep] 9.4.
- Since version 9.5, artifacts are [browsable], when object storage is enabled. - Since version 9.5, artifacts are [browsable], when object storage is enabled.
9.4 lacks this feature. 9.4 lacks this feature.
> Available in [GitLab Premium](https://about.gitlab.com/products/) and
[GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
> Since version 10.6, available in [GitLab CE](https://about.gitlab.com/products/) > Since version 10.6, available in [GitLab CE](https://about.gitlab.com/products/)
If you don't want to use the local disk where GitLab is installed to store the If you don't want to use the local disk where GitLab is installed to store the
......
...@@ -48,10 +48,10 @@ _The uploads are stored by default in ...@@ -48,10 +48,10 @@ _The uploads are stored by default in
1. Save the file and [restart GitLab][] for the changes to take effect. 1. Save the file and [restart GitLab][] for the changes to take effect.
### Using object storage ### Using object storage **[PREMIUM]**
>**Notes:** >**Notes:**
- [Introduced][ee-3867] in [GitLab Enterprise Edition Premium][eep] 10.5. - [Introduced][ee-3867] in [GitLab Premium][eep] 10.5.
If you don't want to use the local disk where GitLab is installed to store the 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. uploads, you can use an object storage provider like AWS S3 instead.
...@@ -205,5 +205,5 @@ _The uploads are stored by default in ...@@ -205,5 +205,5 @@ _The uploads are stored by default in
[reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab" [reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
[restart gitlab]: restart_gitlab.md#installations-from-source "How to restart GitLab" [restart gitlab]: restart_gitlab.md#installations-from-source "How to restart GitLab"
[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium" [eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Premium"
[ee-3867]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3867 [ee-3867]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3867
# Using GitLab CI/CD with a Bitbucket Cloud repository # Using GitLab CI/CD with a Bitbucket Cloud repository **[PREMIUM]**
GitLab CI/CD can be used with Bitbucket Cloud by creating a GitLab CI/CD can be used with Bitbucket Cloud by creating a
[CI/CD project](../../user/project/ci_cd_for_external_repo.md) and connecting [CI/CD project](../../user/project/ci_cd_for_external_repo.md) and connecting
......
# Using GitLab CI/CD with a GitHub repository # Using GitLab CI/CD with a GitHub repository **[PREMIUM]**
GitLab CI/CD can be used with **GitHub.com** and **GitHub Enterprise** by GitLab CI/CD can be used with **GitHub.com** and **GitHub Enterprise** by
creating a [CI/CD project][cicd-projects] to connect your GitHub repository to creating a [CI/CD project][cicd-projects] to connect your GitHub repository to
......
# GitLab CI/CD for external repositories # GitLab CI/CD for external repositories **[PREMIUM]**
>[Introduced][ee-4642] in [GitLab Premium][eep] 10.6. >[Introduced][ee-4642] in [GitLab Premium][eep] 10.6.
...@@ -21,7 +21,6 @@ registry, wiki, and snippets disabled. These features ...@@ -21,7 +21,6 @@ registry, wiki, and snippets disabled. These features
![CI/CD for external repository project creation](img/ci_cd_for_external_repo.png) ![CI/CD for external repository project creation](img/ci_cd_for_external_repo.png)
[ee-4642]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4642 [ee-4642]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4642
[eep]: https://about.gitlab.com/products/ [eep]: https://about.gitlab.com/products/
[mirroring]: ../../workflow/repository_mirroring.md [mirroring]: ../../workflow/repository_mirroring.md
......
# Multi-project pipeline graphs # Multi-project pipeline graphs **[PREMIUM]**
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/2121) in > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/2121) in
[GitLab Premium 9.3](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs). [GitLab Premium 9.3](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs).
......
...@@ -191,13 +191,11 @@ by name. The order of severity is: ...@@ -191,13 +191,11 @@ by name. The order of severity is:
![Pipeline mini graph sorting](img/pipelines_mini_graph_sorting.png) ![Pipeline mini graph sorting](img/pipelines_mini_graph_sorting.png)
### Multi-project pipelines graphs ### Multi-project pipelines graphs **[PREMIUM]**
With [multi-project pipeline graphs](multi_project_pipeline_graphs.md), With [multi-project pipeline graphs](multi_project_pipeline_graphs.md),
you can visualize cross-project pipelines. you can visualize cross-project pipelines.
It is available only in [GitLab Premium][eep].
## How the pipeline duration is calculated ## How the pipeline duration is calculated
Total running time for a given pipeline would exclude retries and pending Total running time for a given pipeline would exclude retries and pending
......
...@@ -21,7 +21,7 @@ A unique trigger token can be obtained when [adding a new trigger](#adding-a-new ...@@ -21,7 +21,7 @@ A unique trigger token can be obtained when [adding a new trigger](#adding-a-new
You can use the `CI_JOB_TOKEN` [variable][predef] (used to authenticate You can use the `CI_JOB_TOKEN` [variable][predef] (used to authenticate
with the [GitLab Container Registry][registry]) in the following cases. with the [GitLab Container Registry][registry]) in the following cases.
#### When used with multi-project pipelines #### When used with multi-project pipelines **[PREMIUM]**
> **Note**: > **Note**:
The use of `CI_JOB_TOKEN` for multi-project pipelines was [introduced][ee-2017] The use of `CI_JOB_TOKEN` for multi-project pipelines was [introduced][ee-2017]
...@@ -45,7 +45,7 @@ Pipelines triggered that way also expose a special variable: ...@@ -45,7 +45,7 @@ Pipelines triggered that way also expose a special variable:
Read more about the [pipelines trigger API][trigapi]. Read more about the [pipelines trigger API][trigapi].
#### When a pipeline depends on the artifacts of another pipeline #### When a pipeline depends on the artifacts of another pipeline **[PREMIUM]**
> **Note**: > **Note**:
The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346] The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346]
......
...@@ -202,7 +202,7 @@ Protected variables can be added by going to your project's ...@@ -202,7 +202,7 @@ Protected variables can be added by going to your project's
Once you set them, they will be available for all subsequent pipelines. Once you set them, they will be available for all subsequent pipelines.
### Limiting environment scopes of secret variables ### Limiting environment scopes of secret variables **[PREMIUM]**
>**Notes:** >**Notes:**
[Introduced][ee-2112] in [GitLab Premium][premium] 9.4. [Introduced][ee-2112] in [GitLab Premium][premium] 9.4.
......
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
comments: false comments: false
--- ---
# Installation # Installation **[CORE ONLY]**
GitLab can be installed via various ways. Check the [installation methods][methods] GitLab can be installed via various ways. Check the [installation methods][methods]
for an overview. for an overview.
...@@ -37,7 +37,7 @@ the full process of installing GitLab on Google Container Engine (GKE), pushing ...@@ -37,7 +37,7 @@ the full process of installing GitLab on Google Container Engine (GKE), pushing
- _Testing only!_ [DigitalOcean and Docker Machine](digitaloceandocker.md) - - _Testing only!_ [DigitalOcean and Docker Machine](digitaloceandocker.md) -
Quickly test any version of GitLab on DigitalOcean using Docker Machine. Quickly test any version of GitLab on DigitalOcean using Docker Machine.
- [GitLab Pivotal Tile](pivotal/index.md) - Install and configure GitLab - [GitLab Pivotal Tile](pivotal/index.md) - Install and configure GitLab
Premium on Pivotal Cloud Foundry. Premium on Pivotal Cloud Foundry. **[PREMIUM ONLY]**
- [Getting started with GitLab and DigitalOcean](https://about.gitlab.com/2016/04/27/getting-started-with-gitlab-and-digitalocean/): requirements, installation process, updates. - [Getting started with GitLab and DigitalOcean](https://about.gitlab.com/2016/04/27/getting-started-with-gitlab-and-digitalocean/): requirements, installation process, updates.
- [Demo: Cloud Native Development with GitLab](https://about.gitlab.com/2017/04/18/cloud-native-demo/): video demonstration on how to install GitLab on Kubernetes, build a project, create Review Apps, store Docker images in Container Registry, deploy to production on Kubernetes, and monitor with Prometheus. - [Demo: Cloud Native Development with GitLab](https://about.gitlab.com/2017/04/18/cloud-native-demo/): video demonstration on how to install GitLab on Kubernetes, build a project, create Review Apps, store Docker images in Container Registry, deploy to production on Kubernetes, and monitor with Prometheus.
......
# GitLab Pivotal Tile # GitLab Pivotal Tile **[PREMIUM ONLY]**
> Introduced in [GitLab Premium][eep] 8.2. > Introduced in [GitLab Premium][eep] 8.2.
......
# GitLab JIRA Development Panel integration # GitLab JIRA Development Panel integration **[PREMIUM]**
> [Introduced][ee-2381] in [GitLab Premium][eep] 10.0. > [Introduced][ee-2381] in [GitLab Premium][eep] 10.0.
......
...@@ -296,7 +296,7 @@ later download and check out. ...@@ -296,7 +296,7 @@ later download and check out.
In GitLab Ultimate, any security warnings are also In GitLab Ultimate, any security warnings are also
[shown in the merge request widget](../../user/project/merge_requests/dast.md). [shown in the merge request widget](../../user/project/merge_requests/dast.md).
### Auto Browser Performance Testing ### Auto Browser Performance Testing **[PREMIUM]**
> Introduced in [GitLab Premium][ee] 10.4. > Introduced in [GitLab Premium][ee] 10.4.
......
# External authorization control # External authorization control **[PREMIUM]**
> >
[Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/4216) in [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/4216) in
......
# SAML SSO for Groups (Beta) # SAML SSO for Groups (Beta) **[PREMIUM]**
> Introduced in [GitLab Premium][https://about.gitlab.com/products/] 10.7. > Introduced in [GitLab Premium][https://about.gitlab.com/products/] 10.7.
......
...@@ -122,17 +122,12 @@ and drag issues around. Read though the ...@@ -122,17 +122,12 @@ and drag issues around. Read though the
[documentation on Issue Boards permissions](project/issue_board.md#permissions) [documentation on Issue Boards permissions](project/issue_board.md#permissions)
to learn more. to learn more.
### File Locking permissions ### File Locking permissions **[PREMIUM]**
> Available in [GitLab Premium](https://about.gitlab.com/products/) and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located. The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located.
Read through the documentation on [permissions for File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html#permissions-on-file-locking) to learn more. Read through the documentation on [permissions for File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html#permissions-on-file-locking) to learn more.
File Locking is available in
[GitLab Premium](https://about.gitlab.com/products/) only.
### Confidential Issues permissions ### Confidential Issues permissions
Confidential issues can be accessed by reporters and higher permission levels, Confidential issues can be accessed by reporters and higher permission levels,
...@@ -195,7 +190,7 @@ will find the option to flag the user as external. ...@@ -195,7 +190,7 @@ will find the option to flag the user as external.
By default new users are not set as external users. This behavior can be changed By default new users are not set as external users. This behavior can be changed
by an administrator under **Admin > Application Settings**. by an administrator under **Admin > Application Settings**.
## Auditor users ## Auditor users **[PREMIUM ONLY]**
>[Introduced][ee-998] in [GitLab Premium][eep] 8.17. >[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
...@@ -282,16 +277,13 @@ for details about the pipelines security model. ...@@ -282,16 +277,13 @@ for details about the pipelines security model.
Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user. Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user.
Read through the documentation on [LDAP users permissions](../administration/auth/how_to_configure_ldap_gitlab_ee/index.md) to learn more. Read through the documentation on [LDAP users permissions](../administration/auth/how_to_configure_ldap_gitlab_ee/index.md) to learn more.
## Auditor users permissions ## Auditor users permissions **[PREMIUM ONLY]**
> Available in [GitLab Premium](https://about.gitlab.com/products/). > Available in [GitLab Premium](https://about.gitlab.com/products/).
An Auditor user should be able to access all projects and groups of a GitLab instance An Auditor user should be able to access all projects and groups of a GitLab instance
with the permissions described on the documentation on [auditor users permissions](https://docs.gitlab.com/ee/administration/auditor_users.html#permissions-and-restrictions-of-an-auditor-user). with the permissions described on the documentation on [auditor users permissions](https://docs.gitlab.com/ee/administration/auditor_users.html#permissions-and-restrictions-of-an-auditor-user).
Auditor users are available in [GitLab Premium](https://about.gitlab.com/products/)
only.
[^1]: On public and internal projects, all users are able to perform this action [^1]: On public and internal projects, all users are able to perform this action
[^2]: Guest users can only view the confidential issues they created themselves [^2]: Guest users can only view the confidential issues they created themselves
[^3]: If **Public pipelines** is enabled in **Project Settings > CI/CD** [^3]: If **Public pipelines** is enabled in **Project Settings > CI/CD**
......
# Canary Deployments # Canary Deployments **[PREMIUM]**
> [Introduced][ee-1659] in [GitLab Premium][eep] 9.1. > [Introduced][ee-1659] in [GitLab Premium][eep] 9.1.
......
...@@ -222,7 +222,7 @@ to reach your apps. This heavily depends on your domain provider, but in case ...@@ -222,7 +222,7 @@ to reach your apps. This heavily depends on your domain provider, but in case
you aren't sure, just create an A record with a wildcard host like you aren't sure, just create an A record with a wildcard host like
`*.example.com.`. `*.example.com.`.
## Setting the environment scope ## Setting the environment scope **[PREMIUM]**
NOTE: **Note:** NOTE: **Note:**
This is only available for [GitLab Premium][ee] where you can add more than This is only available for [GitLab Premium][ee] where you can add more than
...@@ -281,7 +281,7 @@ The result will then be: ...@@ -281,7 +281,7 @@ The result will then be:
- The staging cluster will be used for the "deploy to staging" job. - The staging cluster will be used for the "deploy to staging" job.
- The production cluster will be used for the "deploy to production" job. - The production cluster will be used for the "deploy to production" job.
## Multiple Kubernetes clusters ## Multiple Kubernetes clusters **[PREMIUM]**
> Introduced in [GitLab Premium][ee] 10.3. > Introduced in [GitLab Premium][ee] 10.3.
...@@ -346,9 +346,7 @@ and add a Kubernetes cluster again. ...@@ -346,9 +346,7 @@ and add a Kubernetes cluster again.
Here's what you can do with GitLab if you enable the Kubernetes integration. Here's what you can do with GitLab if you enable the Kubernetes integration.
### Deploy Boards ### Deploy Boards **[PREMIUM]**
> Available in [GitLab Premium][ee].
GitLab's Deploy Boards offer a consolidated view of the current health and GitLab's Deploy Boards offer a consolidated view of the current health and
status of each CI [environment](../../../ci/environments.md) running on Kubernetes, status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
...@@ -358,9 +356,7 @@ workflow they already use without any need to access Kubernetes. ...@@ -358,9 +356,7 @@ workflow they already use without any need to access Kubernetes.
[> Read more about Deploy Boards](../deploy_boards.md) [> Read more about Deploy Boards](../deploy_boards.md)
### Canary Deployments ### Canary Deployments **[PREMIUM]**
> Available in [GitLab Premium][ee].
Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments) Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
and visualize your canary deployments right inside the Deploy Board, without and visualize your canary deployments right inside the Deploy Board, without
......
# Deploy Boards # Deploy Boards **[PREMIUM]**
> [Introduced][ee-1589] in [GitLab Premium][ee] 9.0. > [Introduced][ee-1589] in [GitLab Premium][ee] 9.0.
......
# File Locking # File Locking **[PREMIUM]**
>**Notes:** >**Notes:**
- [Introduced][ee-440] in [GitLab Premium][ee] 8.9. - [Introduced][ee-440] in [GitLab Premium][ee] 8.9.
......
...@@ -81,9 +81,7 @@ GitLab CI/CD build environment: ...@@ -81,9 +81,7 @@ GitLab CI/CD build environment:
Here's what you can do with GitLab if you enable the Kubernetes integration. Here's what you can do with GitLab if you enable the Kubernetes integration.
### Deploy Boards ### Deploy Boards **[PREMIUM]**
> Available in [GitLab Premium][ee].
GitLab's Deploy Boards offer a consolidated view of the current health and GitLab's Deploy Boards offer a consolidated view of the current health and
status of each CI [environment](../../../ci/environments.md) running on Kubernetes, status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
...@@ -93,9 +91,7 @@ workflow they already use without any need to access Kubernetes. ...@@ -93,9 +91,7 @@ workflow they already use without any need to access Kubernetes.
[> Read more about Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html) [> Read more about Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html)
### Canary Deployments ### Canary Deployments **[PREMIUM]**
> Available in [GitLab Premium][ee].
Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments) Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
and visualize your canary deployments right inside the Deploy Board, without and visualize your canary deployments right inside the Deploy Board, without
......
...@@ -91,7 +91,7 @@ GitLab will automatically scan the Prometheus server for metrics from known serv ...@@ -91,7 +91,7 @@ GitLab will automatically scan the Prometheus server for metrics from known serv
You can view the performance dashboard for an environment by [clicking on the monitoring button](../../../ci/environments.md#monitoring-environments). You can view the performance dashboard for an environment by [clicking on the monitoring button](../../../ci/environments.md#monitoring-environments).
### Adding additional metrics ### Adding additional metrics **[PREMIUM]**
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3799) in [GitLab Premium](https://about.gitlab.com/products/) 10.6. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3799) in [GitLab Premium](https://about.gitlab.com/products/) 10.6.
......
...@@ -59,15 +59,12 @@ supported. ...@@ -59,15 +59,12 @@ supported.
![Bottom of a project issues page](img/new_issue_from_email.png) ![Bottom of a project issues page](img/new_issue_from_email.png)
## New issue via Service Desk ## New issue via Service Desk **[PREMIUM]**
Enable [Service Desk](../service_desk.md) to your project and offer email support. Enable [Service Desk](../service_desk.md) to your project and offer email support.
By doing so, when your customer sends a new email, a new issue can be created in By doing so, when your customer sends a new email, a new issue can be created in
the appropriate project and followed up from there. the appropriate project and followed up from there.
_Service Desk is available only for [GitLab Premium](https://about.gitlab.com/products/)
and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/) subscribers._
## New issue from the group-level Issue Tracker ## New issue from the group-level Issue Tracker
Head to the Group dashboard and click "Issues" in the sidebar to visit the Issue Tracker Head to the Group dashboard and click "Issues" in the sidebar to visit the Issue Tracker
......
...@@ -88,9 +88,9 @@ From the group epic list page, you can [filter](../search/index.md#issues-and-me ...@@ -88,9 +88,9 @@ From the group epic list page, you can [filter](../search/index.md#issues-and-me
### Filtering in issue boards ### Filtering in issue boards
- From [project boards](issue_board.md), you can filter by both group labels and project labels in the [search and filter bar](../search/index.md#issue-boards). - From [project boards](issue_board.md), you can filter by both group labels and project labels in the [search and filter bar](../search/index.md#issue-boards).
- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [search and filter bar](../search/index.md#issue-boards) (available in GitLab Premium). - From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [search and filter bar](../search/index.md#issue-boards). **[PREMIUM]**
- From [project boards](issue_board.md), you can filter by both group labels and project labels in the [issue board configuration](issue_board.md#board-with-configuration) (available in GitLab Premium). - From [project boards](issue_board.md), you can filter by both group labels and project labels in the [issue board configuration](issue_board.md#board-with-configuration). **[PREMIUM]**
- From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [issue board configuration](issue_board.md#board-with-configuration) (available in GitLab Premium). - From [group issue boards](issue_board.md#group-issue-boards), you can filter by only group labels in the [issue board configuration](issue_board.md#board-with-configuration). **[PREMIUM]**
## Subscribing to labels ## Subscribing to labels
......
# Browser Performance Testing # Browser Performance Testing **[PREMIUM]**
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3507) in [GitLab Premium](https://about.gitlab.com/products/) 10.3. > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3507) in [GitLab Premium](https://about.gitlab.com/products/) 10.3.
......
...@@ -40,7 +40,7 @@ With **[GitLab Enterprise Edition][ee]**, you can also: ...@@ -40,7 +40,7 @@ With **[GitLab Enterprise Edition][ee]**, you can also:
- Analyze your dependencies for vulnerabilities with [Dependency Scanning](#dependency-scanning) (available in GitLab Ultimate) - Analyze your dependencies for vulnerabilities with [Dependency Scanning](#dependency-scanning) (available in GitLab Ultimate)
- Analyze your Docker images for vulnerabilities with [Container Scanning](#container-scanning) (available in GitLab Ultimate) - Analyze your Docker images for vulnerabilities with [Container Scanning](#container-scanning) (available in GitLab Ultimate)
- Analyze your running web applications for vulnerabilities with [Dynamic Application Security Testing](#dynamic-application-security-testing) (available in GitLab Ultimate) - Analyze your running web applications for vulnerabilities with [Dynamic Application Security Testing](#dynamic-application-security-testing) (available in GitLab Ultimate)
- Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) (available in GitLab Premium) - Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) **[PREMIUM]**
## Use cases ## Use cases
...@@ -282,7 +282,7 @@ merge request widget area. ...@@ -282,7 +282,7 @@ merge request widget area.
[Read more about Dynamic Application Security Testing reports.](dast.md) [Read more about Dynamic Application Security Testing reports.](dast.md)
## Browser Performance Testing ## Browser Performance Testing **[PREMIUM]**
> Introduced in [GitLab Premium][products] 10.3. > Introduced in [GitLab Premium][products] 10.3.
......
...@@ -64,7 +64,7 @@ From the project issue/merge request list pages and the group issue/merge reques ...@@ -64,7 +64,7 @@ From the project issue/merge request list pages and the group issue/merge reques
### Filtering in issue boards ### Filtering in issue boards
- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [search and filter bar](../../search/index.md#issue-boards). - From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [search and filter bar](../../search/index.md#issue-boards).
- From [group issue boards](../issue_board.md#group-issue-boards) (available in [GitLab Premium](https://about.gitlab.com/products), you can filter by only group milestones in the [search and filter bar](../../search/index.md#issue-boards). - From [group issue boards](../issue_board.md#group-issue-boards), you can filter by only group milestones in the [search and filter bar](../../search/index.md#issue-boards). **[PREMIUM]**
- From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[STARTER]** - From [project issue boards](../issue_board.md), you can filter by both group milestones and project milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[STARTER]**
- From [group issue boards](../issue_board.md#group-issue-boards) you can filter by only group milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[PREMIUM]** - From [group issue boards](../issue_board.md#group-issue-boards) you can filter by only group milestones in the [issue board configuration](../issue_board.md#board-with-configuration). **[PREMIUM]**
......
...@@ -163,14 +163,10 @@ Select branches to compare and view the changes inline: ...@@ -163,14 +163,10 @@ Select branches to compare and view the changes inline:
Find it under your project's **Repository > Compare**. Find it under your project's **Repository > Compare**.
## Locked files ## Locked files **[PREMIUM]**
> Available in [GitLab Premium](https://about.gitlab.com/products/). [Lock your files](https://docs.gitlab.com/ee/user/project/file_lock.html) to
prevent any conflicting changes.
Lock your files to prevent any conflicting changes.
[File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) is available only in
[GitLab Premium](https://about.gitlab.com/products/).
## Repository's API ## Repository's API
......
# Service Desk # Service Desk **[PREMIUM]**
> [Introduced][ee-149] in [GitLab Premium 9.1][eep-9.1]. > [Introduced][ee-149] in [GitLab Premium 9.1][eep-9.1].
......
...@@ -40,9 +40,9 @@ Set up your project's merge request settings: ...@@ -40,9 +40,9 @@ Set up your project's merge request settings:
![project's merge request settings](img/merge_requests_settings.png) ![project's merge request settings](img/merge_requests_settings.png)
### Service Desk ### Service Desk **[PREMIUM]**
Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support. Service Desk is available in [GitLab Premium](https://about.gitlab.com/products/). Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support.
### Export project ### Export project
......
...@@ -44,9 +44,9 @@ comments: false ...@@ -44,9 +44,9 @@ comments: false
- [Merge requests versions](../user/project/merge_requests/versions.md) - [Merge requests versions](../user/project/merge_requests/versions.md)
- ["Work In Progress" merge requests](../user/project/merge_requests/work_in_progress_merge_requests.md) - ["Work In Progress" merge requests](../user/project/merge_requests/work_in_progress_merge_requests.md)
- [Fast-forward merge requests](../user/project/merge_requests/fast_forward_merge.md) - [Fast-forward merge requests](../user/project/merge_requests/fast_forward_merge.md)
- (EE) [Merge request approvals](../user/project/merge_requests/merge_request_approvals.md) - [Merge request approvals](../user/project/merge_requests/merge_request_approvals.md) **[STARTER]**
- (EE) [Repository mirroring](repository_mirroring.md) - [Repository mirroring](repository_mirroring.md) **[STARTER]**
- (EE Premium) [Service Desk](../user/project/service_desk.md) - [Service Desk](../user/project/service_desk.md) **[PREMIUM]**
- [Manage large binaries with Git LFS](lfs/manage_large_binaries_with_git_lfs.md) - [Manage large binaries with Git LFS](lfs/manage_large_binaries_with_git_lfs.md)
- [Importing from SVN, GitHub, Bitbucket, etc](importing/README.md) - [Importing from SVN, GitHub, Bitbucket, etc](importing/README.md)
- [Todos](todos.md) - [Todos](todos.md)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment