Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add GitLab references to Changes Detection docs #28212

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add GitLab references to Changes Detection docs #28212

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 29 additions & 1 deletion content/en/continuous_delivery/features/code_changes_detection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,16 @@ To confirm that the setup is valid, select your GitHub App in the [GitHub integr
[2]: https://app.datadoghq.com/integrations/github/
{{% /tab %}}

{{% tab "GitLab" %}}
<div class="alert alert-warning">Datadog's GitLab integration is in Preview. To request access to Datadog's GitLab integration for your organization, reach out to <a href="https://www.datadoghq.com/support/">Datadog Support</a>.</div>

After your organization has access, follow the [GitLab installation guide][1].

**Note**: The scope of the service account's personal access token needs to be at least `read_api`.

[1]: https://github.com/DataDog/gitlab-integration-setup?tab=readme-ov-file#datadog--gitlab-integration-installation-guide
{{% /tab %}}

{{% tab "Other Git Providers" %}}

You can upload your Git repository metadata with the [`datadog-ci git-metadata upload`][1] command.
Expand Down Expand Up @@ -102,10 +112,13 @@ To correctly understand the code changes that a deployment has introduced, only

This can be done in [Software Catalog][5] by specifying, for the interested services, the source code glob file path patterns in the [service definition][4].

If the service definition contains a **full** GitHub URL to the application folder, a single path pattern is automatically used.
If the service definition contains a **full** GitHub or GitLab URL to the application folder, a single path pattern is automatically used.

**Example (schema version v2.2):**

{{< tabs >}}
{{% tab "GitHub" %}}

```yaml
links:
- name: shopist
Expand All @@ -114,6 +127,21 @@ links:
url: https://github.com/organization/example-repository/tree/main/src/apps/shopist
```

{{% /tab %}}

{{% tab "GitLab" %}}

```yaml
links:
- name: shopist
type: repo
provider: gitlab
url: https://gitlab.com/organization/example-repository/-/tree/main/src/apps/shopist?ref_type=heads
```

{{% /tab %}}
{{< /tabs >}}

Code Changes Detection for deployments of the `shopist` service will only consider the Git commits that include changes within the `src/apps/shopist/**` path. You can configure more granular control of the filtering with `extensions[datadoghq.com/cd-visibility]`.

**Example (schema version v2.2):**
Expand Down
Loading