diff --git a/content/en/continuous_delivery/deployments/argocd.md b/content/en/continuous_delivery/deployments/argocd.md index 5f2c8dd2308ae..0b5500b28ac9c 100644 --- a/content/en/continuous_delivery/deployments/argocd.md +++ b/content/en/continuous_delivery/deployments/argocd.md @@ -271,7 +271,7 @@ If notifications are not sent, examine the logs of the `argocd-notification-cont [11]: https://app.datadoghq.com/organization-settings/api-keys [12]: https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/subscriptions/ [13]: /tracing/software_catalog -[14]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/deployment#correlate +[14]: https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-deployment#correlate [15]: /containers/kubernetes [16]: https://app.datadoghq.com/orchestration/explorer [17]: https://argo-cd.readthedocs.io/en/stable/user-guide/best_practices/#separating-config-vs-source-code-repositories diff --git a/content/en/continuous_delivery/features/code_changes_detection.md b/content/en/continuous_delivery/features/code_changes_detection.md index 85d5f04cbd9a5..fcd7d38896098 100644 --- a/content/en/continuous_delivery/features/code_changes_detection.md +++ b/content/en/continuous_delivery/features/code_changes_detection.md @@ -98,7 +98,7 @@ Reporting commit 007f7f466e035b052415134600ea899693e7bb34 from repository git@gi ✅ Handled in 0.077 seconds. ``` -[1]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/git-metadata +[1]: https://github.com/DataDog/datadog-ci/tree/master/packages/base/src/commands/git-metadata {{% /tab %}} {{< /tabs >}} @@ -168,9 +168,9 @@ extensions: - "**" ``` -In this case, Code Changes Detection for deployments of the `shopist` service will consider the Git commits that include changes in the whole repository tree. +In this case, Code Changes Detection for deployments of the `shopist` service will consider the Git commits that include changes in the whole repository tree. -
If a pattern is exactly ** or begins with it, enclose it in quotes, as * is reserved in YAML for anchors.
+
If a pattern is exactly ** or begins with it, enclose it in quotes, as * is reserved in YAML for anchors.
## Further Reading diff --git a/content/en/continuous_delivery/features/rollbacks_detection.md b/content/en/continuous_delivery/features/rollbacks_detection.md index b721ac1dc2624..de363cf7d58ef 100644 --- a/content/en/continuous_delivery/features/rollbacks_detection.md +++ b/content/en/continuous_delivery/features/rollbacks_detection.md @@ -54,5 +54,5 @@ When images are properly correlated, Datadog populates a version tag from the im {{< partial name="whats-next/whats-next.html" >}} [1]: https://app.datadoghq.com/ci/deployments/executions -[2]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/deployment#correlate +[2]: https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-deployment#correlate [3]: /continuous_delivery/deployments/argocd#correlate-deployments-with-ci-pipelines diff --git a/content/en/continuous_testing/cicd_integrations/gitlab.md b/content/en/continuous_testing/cicd_integrations/gitlab.md index 42f5396e8c7ae..63acfabeb1d03 100644 --- a/content/en/continuous_testing/cicd_integrations/gitlab.md +++ b/content/en/continuous_testing/cicd_integrations/gitlab.md @@ -32,11 +32,11 @@ For more information, see [CI/CD Integrations Configuration][4]. ### Run tests using test IDs {{< code-block lang="yaml" >}} -stages: +stages: - test synthetic-tests: stage: test - script: + script: - npm install -g @datadog/datadog-ci - datadog-ci synthetics run-tests --apiKey "$DATADOG_API_KEY" --appKey "$DATADOG_APP_KEY" --public-id xtf-w5p-z5n --public-id eif-van-tu7 {{< /code-block >}} @@ -44,25 +44,25 @@ synthetic-tests: ### Run tests using tags {{< code-block lang="yaml" >}} -stages: +stages: - test synthetic-tests: stage: test - script: + script: - npm install -g @datadog/datadog-ci - datadog-ci synthetics run-tests --apiKey "$DATADOG_API_KEY" --appKey "$DATADOG_APP_KEY" -s 'tag:e2e-tests' {{< /code-block >}} ### Run tests using variable overrides -If you have different test users or data specific to your CI/CD environment, you can override these variables with the `-v` command. For more information, [see the Synthetics command](https://github.com/DataDog/datadog-ci/tree/master/src/commands/synthetics) in the `datadog-ci` NPM package. +If you have different test users or data specific to your CI/CD environment, you can override these variables with the `-v` command. For more information, [see the Synthetics command](https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-synthetics) in the `datadog-ci` NPM package. {{< code-block lang="yaml" >}} -stages: +stages: - test synthetic-tests: stage: test - script: + script: - npm install -g @datadog/datadog-ci - datadog-ci synthetics run-tests --apiKey "$DATADOG_API_KEY" --appKey "$DATADOG_APP_KEY" -s 'tag:e2e-tests' -v PASSWORD="$PASSWORD" {{< /code-block >}} @@ -74,11 +74,11 @@ synthetic-tests: Add a custom `config.json` file to your pipeline repository and access it in your pipeline configuration. {{< code-block lang="yaml" >}} -stages: +stages: - test synthetic-tests: stage: test - script: + script: - npm install -g @datadog/datadog-ci - datadog-ci synthetics run-tests --apiKey "$DATADOG_API_KEY" --appKey "$DATADOG_APP_KEY" --config synthetics_global.json -f synthetic_test.json {{< /code-block >}} diff --git a/content/en/deployment_gates/setup.md b/content/en/deployment_gates/setup.md index d3c9dd7a6a8ec..ea34ce99836b3 100644 --- a/content/en/deployment_gates/setup.md +++ b/content/en/deployment_gates/setup.md @@ -136,7 +136,7 @@ For complete configuration options and detailed usage examples, refer to the [`d [1]: https://github.com/DataDog/datadog-ci [2]: https://app.datadoghq.com/organization-settings/api-keys [3]: https://app.datadoghq.com/organization-settings/application-keys -[4]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/deployment#gate +[4]: https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-deployment#gate {{% /tab %}} {{% tab "Argo Rollouts" %}} @@ -234,7 +234,7 @@ spec: [4]: https://argo-rollouts.readthedocs.io/en/stable/features/analysis/#analysis-template-arguments [5]: https://app.datadoghq.com/organization-settings/api-keys [6]: https://app.datadoghq.com/organization-settings/application-keys -[7]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/deployment#gate +[7]: https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-deployment#gate {{% /tab %}} {{% tab "Generic script" %}} diff --git a/content/en/dora_metrics/setup/deployments.md b/content/en/dora_metrics/setup/deployments.md index 1b3a97d1550c9..d45938b4f81b6 100644 --- a/content/en/dora_metrics/setup/deployments.md +++ b/content/en/dora_metrics/setup/deployments.md @@ -238,7 +238,7 @@ Reporting commit 007f7f466e035b052415134600ea899693e7bb34 from repository git@gi ✅ Handled in 0.077 seconds. ``` -[1]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/git-metadata +[1]: https://github.com/DataDog/datadog-ci/tree/master/packages/base/src/commands/git-metadata {{% /tab %}} {{< /tabs >}} diff --git a/content/en/glossary/terms/test_suite.md b/content/en/glossary/terms/test_suite.md index ea4c4bcebd6b1..dd2710786f306 100644 --- a/content/en/glossary/terms/test_suite.md +++ b/content/en/glossary/terms/test_suite.md @@ -7,4 +7,4 @@ core_product: related_terms: - test service --- -In Datadog Synthetic Monitoring and Test Optimization, a test suite is generally a group of tests exercising the same unit of code depending on your language and testing framework. You can access an example of a test suite which corresponds to a test file in the `datadog-ci` repository. For more information, see the documentation. +In Datadog Synthetic Monitoring and Test Optimization, a test suite is generally a group of tests exercising the same unit of code depending on your language and testing framework. You can access an example of a test suite which corresponds to a test file in the `datadog-ci` repository. For more information, see the documentation. diff --git a/content/en/integrations/guide/source-code-integration.md b/content/en/integrations/guide/source-code-integration.md index aa83c946a7bd2..30e5994ad4bca 100644 --- a/content/en/integrations/guide/source-code-integration.md +++ b/content/en/integrations/guide/source-code-integration.md @@ -51,8 +51,8 @@ Datadog supports the following features for the following source code management | **Connect SaaS Instance** | Yes
(GitHub.com and GitHub Enterprise Cloud) | Yes
(GitLab.com) | Yes
(Azure DevOps Services) | No
(Bitbucket.org) | | **Connect On-Prem Instance** | Yes
(GitHub Enterprise Server) | Yes
(GitLab Self-Managed or Dedicated) | No
(Azure DevOps Server) | No
(Bitbucket Data Center or Server)| | **Context Links** | Yes | Yes | Yes | Yes | -| **Code Snippets** | Yes | Yes | Yes | No | -| **PR Comments** | Yes | Yes | Yes | No | +| **Code Snippets** | Yes | Yes | Yes | No | +| **PR Comments** | Yes | Yes | Yes | No | {{< tabs >}} {{% tab "GitHub (SaaS & On-Prem)" %}} @@ -117,7 +117,7 @@ Successfully synced git DB in 3.579 seconds. ✅ Uploaded in 5.207 seconds. ``` -[1]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/git-metadata +[1]: https://github.com/DataDog/datadog-ci/tree/master/packages/base/src/commands/git-metadata {{% /tab %}} {{< /tabs >}} @@ -577,7 +577,7 @@ For more information, see the [Dynamic Instrumentation documentation][102]. {{< tabs >}} {{% tab "CI Visibility" %}} -PR comments are enabled by default when first onboarding to CI Visibility if the GitHub or GitLab integration is installed correctly. These integrations post a comment summarizing the failed jobs detected in your pull request. +PR comments are enabled by default when first onboarding to CI Visibility if the GitHub or GitLab integration is installed correctly. These integrations post a comment summarizing the failed jobs detected in your pull request. {{< img src="integrations/guide/source_code_integration/ci-visibility-pr-comment.png" alt="PR Comment summarizing failed jobs detected by CI Visibility" style="width:100%;">}} @@ -588,9 +588,9 @@ To disable PR comments for CI Visibility, go to the [CI Visibility Repository Se {{% /tab %}} {{% tab "Code Security" %}} -PR comments are enabled by default when first onboarding to Code Security if the GitHub, GitLab, or Azure DevOps integration is installed correctly. These integrations post two types of comments on your pull requests: +PR comments are enabled by default when first onboarding to Code Security if the GitHub, GitLab, or Azure DevOps integration is installed correctly. These integrations post two types of comments on your pull requests: -1. A single comment summarizing the new violations detected in your pull request. +1. A single comment summarizing the new violations detected in your pull request. {{< img src="integrations/guide/source_code_integration/code-security-summary-pr-comment.png" alt="PR Comment summarizing the new violations detected by Code Security" style="width:100%;">}} @@ -605,7 +605,7 @@ To disable PR comments for Code Security, go to the [Code Security Repository Se {{% /tab %}} {{% tab "Test Optimization" %}} -PR comments are enabled by default when first onboarding to Test Optimization if the GitHub or GitLab integration is installed correctly. The integration posts a comment summarizing the failed and flaky tests detected in your pull request. +PR comments are enabled by default when first onboarding to Test Optimization if the GitHub or GitLab integration is installed correctly. The integration posts a comment summarizing the failed and flaky tests detected in your pull request. {{< img src="integrations/guide/source_code_integration/test-optimization-pr-comment.png" alt="PR Comment summarizing failed and flaky tests detected by Test Optimization" style="width:100%;">}} diff --git a/content/en/quality_gates/setup/_index.md b/content/en/quality_gates/setup/_index.md index 12b92aeb3d19c..8017a3166089f 100644 --- a/content/en/quality_gates/setup/_index.md +++ b/content/en/quality_gates/setup/_index.md @@ -27,19 +27,19 @@ To create a Quality Gates rule in Datadog: You can create a rule that is evaluated only on specific repositories and branches. To customize the rule scope, click `Select when to evaluate` and specify the branch or repository that should be included or excluded. - To add a custom scope (such as a team name), click **+ Add Filter** and select **Custom scope**. Enter a tag name without spaces (such as `documentation` or `team-documentation`) and click **Add Custom Scope**. Enter values that should be included or excluded. - + To add a custom scope (such as a team name), click **+ Add Filter** and select **Custom scope**. Enter a tag name without spaces (such as `documentation` or `team-documentation`) and click **Add Custom Scope**. Enter values that should be included or excluded. + When adding a custom scope to a rule, custom scopes must be passed to the `datadog-ci gate evaluate` command using the `--scope` option. For more information, see [Understanding Rule Scopes][13]. 4. Define the rule conditions. The rule condition states in which scenario the rule fails, failing the related pipeline (if the rule is blocking). You can select one of the existing rule conditions for the rule type you have selected. If the rule scope is set to `always evaluate`, the rule is evaluated on all repositories and branches. - + The following example demonstrates how to create a Static Analysis rule that fails when one or more Static Analysis code quality violations with `error` status are contained within a repository. - Select **Static Analysis** for the rule type and click `Always evaluate` for the rule scope. + Select **Static Analysis** for the rule type and click `Always evaluate` for the rule scope. {{< img src="quality_gates/setup/static_analysis_2.png" alt="A Static Analysis rule that fails when any code quality violations with an error status are contained in any service" style="width:100%" >}} - In the **Define rule conditions** section, select `code quality violations` from the dropdown menu. Then, select the `error` status type, select `above or equal to`, and enter the value of `1`. + In the **Define rule conditions** section, select `code quality violations` from the dropdown menu. Then, select the `error` status type, select `above or equal to`, and enter the value of `1`. 5. Specify a rule name that describes the rule that you are creating. 6. Select whether the rule should block the pipeline when it fails. Non-blocking rules are helpful when you roll out a new rule and want to verify its behavior before making it blocking. @@ -112,7 +112,7 @@ After the permission is granted, you can see the checks in GitHub. ## Manage rules -You can edit and delete Quality Gates rules by hovering over a rule on the [**Quality Gates Rules** page][2]. +You can edit and delete Quality Gates rules by hovering over a rule on the [**Quality Gates Rules** page][2]. {{< img src="quality_gates/setup/delete_2.png" alt="Edit, clone, or delete a Quality Gates rule" style="width:100%;">}} @@ -131,7 +131,7 @@ For more information, see the [RBAC Permissions documentation][1]. [1]: /account_management/rbac/permissions [2]: https://app.datadoghq.com/ci/quality-gates [3]: /account_management/audit_trail/events/#ci-visibility-events -[4]: https://github.com/DataDog/datadog-ci/blob/master/packages/datadog-ci/src/commands/gate/README.md +[4]: https://github.com/DataDog/datadog-ci/blob/master/packages/plugin-gate/README.md [5]: https://app.datadoghq.com/organization-settings/api-keys [6]: https://app.datadoghq.com/organization-settings/application-keys [7]: https://github.com/DataDog/datadog-ci/blob/master/README.md diff --git a/content/en/real_user_monitoring/error_tracking/mobile/flutter.md b/content/en/real_user_monitoring/error_tracking/mobile/flutter.md index e179295fa7f5e..c83b9b0497cfa 100644 --- a/content/en/real_user_monitoring/error_tracking/mobile/flutter.md +++ b/content/en/real_user_monitoring/error_tracking/mobile/flutter.md @@ -157,9 +157,9 @@ datadog-ci flutter-symbols upload --service-name --dart-symb [2]: https://app.datadoghq.com/rum/application/create [3]: https://docs.datadoghq.com/real_user_monitoring/mobile_and_tv_monitoring/flutter/setup [4]: https://www.npmjs.com/package/@datadog/datadog-ci -[5]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/flutter-symbols +[5]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/flutter-symbols [6]: https://pub.dev/documentation/datadog_flutter_plugin/latest/datadog_flutter_plugin/DatadogConfiguration-class.html [7]: https://docs.flutter.dev/deployment/flavors [8]: https://pub.dev/documentation/datadog_flutter_plugin/latest/datadog_flutter_plugin/DatadogConfiguration/flavor.html [9]: https://pub.dev/documentation/datadog_flutter_plugin/latest/datadog_flutter_plugin/DatadogConfiguration/version.html -[10]: https://app.datadoghq.com/source-code/setup/rum \ No newline at end of file +[10]: https://app.datadoghq.com/source-code/setup/rum diff --git a/content/en/real_user_monitoring/error_tracking/mobile/reactnative.md b/content/en/real_user_monitoring/error_tracking/mobile/reactnative.md index e5374ef25acfa..122ada141e50c 100644 --- a/content/en/real_user_monitoring/error_tracking/mobile/reactnative.md +++ b/content/en/real_user_monitoring/error_tracking/mobile/reactnative.md @@ -499,7 +499,7 @@ Inside the loop, add the following snippet: [9]: https://fastlane.tools/ [10]: https://appcenter.ms/ [11]: https://www.bitrise.io/ -[12]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/react-native#xcode +[12]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/react-native#xcode [13]: https://github.com/DataDog/datadog-react-native-wizard [14]: https://github.com/DataDog/react-native-performance-limiter [15]: https://plugins.gradle.org/plugin/com.datadoghq.dd-sdk-android-gradle-plugin diff --git a/content/en/real_user_monitoring/guide/upload-javascript-source-maps.md b/content/en/real_user_monitoring/guide/upload-javascript-source-maps.md index 0c95e53335263..cb00a1a2321b6 100644 --- a/content/en/real_user_monitoring/guide/upload-javascript-source-maps.md +++ b/content/en/real_user_monitoring/guide/upload-javascript-source-maps.md @@ -21,7 +21,7 @@ If your front-end JavaScript source code is minified, upload your source maps to ## Instrument your code -Configure your JavaScript bundler such that when minifying your source code, it generates source maps that directly include the related source code in the `sourcesContent` attribute. +Configure your JavaScript bundler such that when minifying your source code, it generates source maps that directly include the related source code in the `sourcesContent` attribute.
Ensure that the size of each source map augmented with the size of the related minified file does not exceed the limit of **500 MB**. @@ -158,7 +158,7 @@ On the other hand, an unminified stack trace provides you with all the context y {{< partial name="whats-next/whats-next.html" >}} -[1]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/sourcemaps +[1]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/sourcemaps [2]: https://docs.datadoghq.com/real_user_monitoring/browser/setup/#initialization-parameters [3]: https://docs.datadoghq.com/logs/log_collection/javascript/#initialization-parameters -[4]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/sourcemaps#link-errors-with-your-source-code +[4]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/sourcemaps#link-errors-with-your-source-code diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/error_tracking.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/error_tracking.md index fe246357e7ddf..8d1ef0e81afb2 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/error_tracking.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/flutter/error_tracking.md @@ -5,7 +5,7 @@ description: "Enable comprehensive crash reporting and error tracking for Flutte ## Overview -Enable Crash Reporting and Error Tracking to get comprehensive crash reports and error trends with Real User Monitoring. +Enable Crash Reporting and Error Tracking to get comprehensive crash reports and error trends with Real User Monitoring. Your crash reports appear in [**Error Tracking**][1]. @@ -32,7 +32,7 @@ final configuration = DdSdkConfiguration( DatadogSdk.instance.initialize(configuration); ``` -If your application suffers a fatal crash, once your application restarts, the Datadog Flutter SDK uploads a crash report to Datadog. For non-fatal errors, the Datadog Flutter SDK uploads these errors with other RUM data. +If your application suffers a fatal crash, once your application restarts, the Datadog Flutter SDK uploads a crash report to Datadog. For non-fatal errors, the Datadog Flutter SDK uploads these errors with other RUM data. ## Upload symbol files to Datadog @@ -54,7 +54,7 @@ First, install the `datadog-ci` tool from the instructions above and create a `d Because this file contains your API key, it should not be checked in to version control. -Alternately, you can set the `DATADOG_API_KEY` and `DATADOG_SITE` environment variables. +Alternately, you can set the `DATADOG_API_KEY` and `DATADOG_SITE` environment variables. Then, you can use the following command to upload all the necessary files for symbolication and deobfuscation of your crash reports: ```sh @@ -89,7 +89,7 @@ Note that Datadog uses tags for versions which do not allow `+`. All tooling aut [2]: https://app.datadoghq.com/rum/application/create [3]: https://docs.datadoghq.com/real_user_monitoring/flutter/#setup [4]: https://www.npmjs.com/package/@datadog/datadog-ci -[6]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/flutter-symbols +[6]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/flutter-symbols [7]: https://pub.dev/documentation/datadog_flutter_plugin/latest/datadog_flutter_plugin/DatadogConfiguration-class.html [8]: https://docs.flutter.dev/deployment/flavors [9]: https://pub.dev/documentation/datadog_flutter_plugin/latest/datadog_flutter_plugin/DatadogConfiguration/flavor.html diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/error_tracking.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/error_tracking.md index c6e54cd00ec3d..e79c37e3241c4 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/error_tracking.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/error_tracking.md @@ -498,7 +498,7 @@ Inside the loop, add the following snippet: [9]: https://fastlane.tools/ [10]: https://appcenter.ms/ [11]: https://www.bitrise.io/ -[12]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/react-native#xcode +[12]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/react-native#xcode [13]: https://github.com/DataDog/datadog-react-native-wizard [14]: https://github.com/DataDog/react-native-performance-limiter [15]: https://plugins.gradle.org/plugin/com.datadoghq.dd-sdk-android-gradle-plugin diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/setup/codepush.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/setup/codepush.md index 3a8f1d7ef9296..d1b379601e0e8 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/setup/codepush.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/react_native/setup/codepush.md @@ -158,10 +158,10 @@ Then, upload your source maps using the [`datadog-ci react-native upload`][5] co ## Sending data when device is offline -RUM ensures availability of data when your user device is offline. In case of low-network areas, or when the device battery is too low, all the RUM events are first stored on the local device in batches. +RUM ensures availability of data when your user device is offline. In case of low-network areas, or when the device battery is too low, all the RUM events are first stored on the local device in batches. Each batch follows the intake specification. They are sent as soon as the network is available, and the battery is high enough to ensure the Datadog SDK does not impact the end user's experience. If the network is not available while your application is in the foreground, or if an upload of data fails, the batch is kept until it can be sent successfully. - + This means that even if users open your application while offline, no data is lost. To ensure the SDK does not use too much disk space, the data on the disk is automatically discarded if it gets too old. ## Further reading @@ -172,5 +172,5 @@ This means that even if users open your application while offline, no data is lo [2]: /real_user_monitoring/reactnative/ [3]: https://github.com/DataDog/datadog-ci [4]: https://docs.microsoft.com/en-us/appcenter/distribution/codepush/rn-api-ref#codepushgetupdatemetadata -[5]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/react-native#upload -[6]: https://github.com/DataDog/dd-sdk-reactnative-examples/tree/main/rum-react-navigation-codepush \ No newline at end of file +[5]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/react-native#upload +[6]: https://github.com/DataDog/dd-sdk-reactnative-examples/tree/main/rum-react-navigation-codepush diff --git a/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/error_tracking.md b/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/error_tracking.md index 186a415e45a1b..286040c49601c 100644 --- a/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/error_tracking.md +++ b/content/en/real_user_monitoring/mobile_and_tv_monitoring/unity/error_tracking.md @@ -108,5 +108,5 @@ To verify your Unity Crash Reporting and Error Tracking configuration, issue an [2]: https://app.datadoghq.com/rum/application/create [3]: /real_user_monitoring/mobile_and_tv_monitoring/setup/unity#setup [4]: https://www.npmjs.com/package/@datadog/datadog-ci -[5]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/unity-symbols +[5]: https://github.com/DataDog/datadog-ci/tree/master/packages/datadog-ci/src/commands/unity-symbols [6]: https://app.datadoghq.com/source-code/setup/rum diff --git a/content/en/synthetics/guide/version_history.md b/content/en/synthetics/guide/version_history.md index 07573bf3468f7..5c12078877d2c 100644 --- a/content/en/synthetics/guide/version_history.md +++ b/content/en/synthetics/guide/version_history.md @@ -16,17 +16,17 @@ Version History automatically tracks changes made to your Synthetic Monitoring t Version History allows you to: -- **Troubleshoot failing tests**: Determine whether a recent change introduced the failure. -- **Collaborate with teammates**: See who made changes and what was updated. -- **Roll back tests**: Restore a previous version after a deployment rollback or incorrect update. -- **Clone tests**: Create test based on a previous version, without changing the current test. +- **Troubleshoot failing tests**: Determine whether a recent change introduced the failure. +- **Collaborate with teammates**: See who made changes and what was updated. +- **Roll back tests**: Restore a previous version after a deployment rollback or incorrect update. +- **Clone tests**: Create test based on a previous version, without changing the current test. - **Support multi-environment testing**: Deploy different test versions to match the code running in each environment, ensuring tests remain compatible with environment-specific deployments. ## Prerequisites -All Synthetic Monitoring tests retain 30 days worth of version history by default. In order to see any previous versions, an edit must be made within the last 30 days. +All Synthetic Monitoring tests retain 30 days worth of version history by default. In order to see any previous versions, an edit must be made within the last 30 days. -With [Audit Trail][1] enabled, the version history is extended from 30 days to 90 days. After enabling Audit Trail, you are able to see any edits made between 30 to 90 days ago on all existing Synthetic tests. +With [Audit Trail][1] enabled, the version history is extended from 30 days to 90 days. After enabling Audit Trail, you are able to see any edits made between 30 to 90 days ago on all existing Synthetic tests. ## View versions @@ -50,11 +50,11 @@ To create a new test based on a previous version without modifying your current ## Run any version -From the Version History side panel, after you choose the version to restore, click the kebab menu to the right of a user profile and select **Run this test version**. +From the Version History side panel, after you choose the version to restore, click the kebab menu to the right of a user profile and select **Run this test version**. {{< img src="/synthetics/guide/version_history/synthetics_run_version.png" alt="Synthetic Monitoring Version history menu, highlighting run this test version" style="width:60%;" >}} -Optionally, click **Copy version ID** to run the test version with the [Datadog CLI][2] or [Datadog API][3]: +Optionally, click **Copy version ID** to run the test version with the [Datadog CLI][2] or [Datadog API][3]: {{< tabs >}} {{% tab "Datadog CLI" %}} @@ -110,5 +110,5 @@ Content-Type: application/json {{< partial name="whats-next/whats-next.html" >}} [1]: /account_management/audit_trail/ -[2]: https://github.com/DataDog/datadog-ci/tree/master/src/commands/synthetics#run-tests-command -[3]: /api/latest/synthetics/#trigger-tests-from-cicd-pipelines \ No newline at end of file +[2]: https://github.com/DataDog/datadog-ci/tree/master/packages/plugin-synthetics#run-tests-command +[3]: /api/latest/synthetics/#trigger-tests-from-cicd-pipelines diff --git a/content/en/tests/explorer/_index.md b/content/en/tests/explorer/_index.md index aa3abd61c29b3..ef7d53be8682f 100644 --- a/content/en/tests/explorer/_index.md +++ b/content/en/tests/explorer/_index.md @@ -15,7 +15,7 @@ further_reading: ## Overview -The Test Optimization Explorer allows you to [search and filter](#search-and-filter), [visualize](#visualize), and [export](#export) test runs at multiple levels using any tag. +The Test Optimization Explorer allows you to [search and filter](#search-and-filter), [visualize](#visualize), and [export](#export) test runs at multiple levels using any tag. Navigate to [**Software Delivery** > **Test Optimization** > **Test Runs**][6] to see your CI test run results across the following levels: **Session**, **Module**, **Suite**, and **Test**. Each test level represents a different level of aggregation of tests. @@ -130,11 +130,11 @@ Select a visualization type to visualize the outcomes of your filters and aggreg [8]: https://app.datadoghq.com/notebook/list [9]: https://learn.microsoft.com/en-us/visualstudio/test/create-a-unit-test-project?view=vs-2022#to-create-a-unit-test-project [10]: https://github.com/realm/SwiftLint/blob/7738f0c0a5990201ca6556bdb2f13f8e67b5191d/Package.swift#L71 -[11]: https://github.com/DataDog/datadog-ci/blob/6de6ea3bbffa57d8576422535061ca35c759feb6/src/commands/junit/__tests__/upload.test.ts +[11]: https://github.com/DataDog/datadog-ci/blob/master/packages/datadog-ci/src/commands/junit/__tests__/upload.test.ts [12]: /glossary/?product=ci-cd#test-service -[13]: /glossary/?product=ci-cd#test-suite +[13]: /glossary/?product=ci-cd#test-suite [14]: /real_user_monitoring/ [15]: /tests/flaky_test_management/early_flake_detection/ [16]: /intelligent_test_runner/ [17]: /tests/code_coverage/ -[18]: https://app.datadoghq.com/ci/test-runs?viz=timeseries \ No newline at end of file +[18]: https://app.datadoghq.com/ci/test-runs?viz=timeseries