Commit 2165c197 authored by mo khan's avatar mo khan

Update the path of license-management to license-finder

parent 00567127
...@@ -195,7 +195,7 @@ see the documentation. ...@@ -195,7 +195,7 @@ see the documentation.
> Introduced in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.0. > Introduced in [GitLab Ultimate](https://about.gitlab.com/pricing/) 11.0.
License Compliance uses the License Compliance uses the
[License Compliance Docker image](https://gitlab.com/gitlab-org/security-products/license-management) [License Compliance Docker image](https://gitlab.com/gitlab-org/security-products/analyzers/license-finder)
to search the project dependencies for their license. The Auto License Compliance stage to search the project dependencies for their license. The Auto License Compliance stage
is skipped on licenses other than [Ultimate](https://about.gitlab.com/pricing/). is skipped on licenses other than [Ultimate](https://about.gitlab.com/pricing/).
......
...@@ -121,7 +121,7 @@ The results will be saved as a ...@@ -121,7 +121,7 @@ The results will be saved as a
[License Compliance report artifact](../../../ci/pipelines/job_artifacts.md#artifactsreportslicense_scanning) [License Compliance report artifact](../../../ci/pipelines/job_artifacts.md#artifactsreportslicense_scanning)
that you can later download and analyze. Due to implementation limitations, we that you can later download and analyze. Due to implementation limitations, we
always take the latest License Compliance artifact available. Behind the scenes, the always take the latest License Compliance artifact available. Behind the scenes, the
[GitLab License Compliance Docker image](https://gitlab.com/gitlab-org/security-products/license-management) [GitLab License Compliance Docker image](https://gitlab.com/gitlab-org/security-products/analyzers/license-finder)
is used to detect the languages/frameworks and in turn analyzes the licenses. is used to detect the languages/frameworks and in turn analyzes the licenses.
The License Compliance settings can be changed through [environment variables](#available-variables) by using the The License Compliance settings can be changed through [environment variables](#available-variables) by using the
...@@ -634,7 +634,7 @@ import the following default License Compliance analyzer images from `registry.g ...@@ -634,7 +634,7 @@ import the following default License Compliance analyzer images from `registry.g
offline [local Docker container registry](../../packages/container_registry/index.md): offline [local Docker container registry](../../packages/container_registry/index.md):
```plaintext ```plaintext
registry.gitlab.com/gitlab-org/security-products/license-management:latest registry.gitlab.com/gitlab-org/security-products/analyzers/license-finder:latest
``` ```
The process for importing Docker images into a local offline Docker registry depends on The process for importing Docker images into a local offline Docker registry depends on
......
# Read more about this feature here: https://docs.gitlab.com/ee/user/application_security/license_compliance/ # Read more about this feature here: https://docs.gitlab.com/ee/user/application_security/license_compliance/
# #
# Configure the scanning tool through the environment variables. # Configure the scanning tool through the environment variables.
# List of the variables: https://gitlab.com/gitlab-org/security-products/license-management#settings # List of the variables: https://gitlab.com/gitlab-org/security-products/analyzers/license-finder#settings
# How to set: https://docs.gitlab.com/ee/ci/yaml/#variables # How to set: https://docs.gitlab.com/ee/ci/yaml/#variables
variables: variables:
......
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