Troubleshooting CI Visibility

Troubleshooting CI Visibility

CI Visibility is not available in the selected site () at this time.

Your Jenkins instance is instrumented, but Datadog isn’t showing any data

  1. Make sure that at least one pipeline has finished executing. Pipeline execution information is only sent after the pipeline has finished.
  2. Make sure the Datadog Agent host is properly configured and it’s reachable by the Datadog Plugin. You can test connectivity by clicking on the Check connectivity with the Datadog Agent button on the Jenkins plugin configuration UI.
  3. If you still don’t see any results, contact Support for troubleshooting help.

Your tests are instrumented, but Datadog isn’t showing any data

  1. Go to the Setup Tracing on CI Tests page for the language you’re instrumenting and check the Compatibility section. Make sure the testing framework you are using is supported.
  2. Check if you see any test results in the Test Runs section. If you do see results there, but not in the Tests section, Git information is missing. See Data appears in Test Runs but not Tests to troubleshoot it.
  3. For languages other than Swift, make sure the Datadog Agent is running on the host where tests are run (accessible at localhost:8126), or if accessible on another hostname or port, make sure you run your tests with the appropriate Agent hostname set in the DD_AGENT_HOST and the appropriate port in DD_TRACE_AGENT_PORT environment variables. You can activate debug mode in the tracer to check if it’s able to connect to the Agent.
  4. If you still don’t see any results, contact Support for troubleshooting help.

Data appears in test runs but not tests

If you can see test results data in the Test Runs tab, but not the Tests tab, Git metadata (repository, commit and/or branch) is probably missing. To confirm this is the case, open a test execution in the Test Runs section, and check that there is no git.repository_url, git.commit.sha, or git.branch. If these tags are not populated, nothing shows in the Tests section.

  1. Tracers first use the environment variables, if any, set by the CI provider to collect Git information. See Running tests inside a container for a list of environment variables that the tracer attempts to read for each supported CI provider. At a minimum, this populates the repository, commit hash, and branch information.

  2. Next, tracers fetch Git metadata using the local .git folder, if present, by executing git commands. This populates all Git metadata fields, including commit message, author, and committer information. Ensure the .git folder is present and the git binary is installed and in $PATH. This information is used to populate attributes not detected in the previous step.

  3. You can also provide Git information manually using environment variables, which override information detected by any of the previous steps. The supported environment variables for providing Git information are the following:

    URL of the repository where the code is stored. Both HTTP and SSH URLs are supported.
    Git branch being tested. Leave empty if providing tag information instead.
    Example: develop
    Git tag being tested (if applicable). Leave empty if providing branch information instead.
    Example: 1.0.1
    Full commit hash.
    Example: a18ebf361cc831f5535e58ec4fae04ffd98d8152
    Commit message.
    Example: Set release number
    Commit author name.
    Example: John Smith
    Commit author email.
    Commit author date in ISO 8601 format.
    Example: 2021-03-12T16:00:28Z
    Commit committer name.
    Example: Jane Smith
    Commit committer email.
    Commit committer date in ISO 8601 format.
    Example: 2021-03-12T16:00:28Z
  4. If no CI provider environment variables are found, tests results are sent with no Git metadata.

Need further help?

If you have another issue, or the above solutions don’t work, contact Support for troubleshooting help.