Tests in Containers
CI Visibility is not available in the selected site () at this time.
If you run your tests inside a container that you launch yourself within the build (for example, using docker run
or docker-compose
), forward the following environment variables to the container depending on your CI provider. This enables the Datadog tracer to autodetect the build information.
Additionally, you need to pass in the environment variables required to configure the tracer as described in the per-language test instrumentation instructions (such as DD_SERVICE
, DD_ENV
, and a valid DD_TRACE_AGENT_URL
that is accessible from within the container).
TF_BUILD
BUILD_DEFINITIONNAME
BUILD_BUILDID
BUILD_SOURCESDIRECTORY
BUILD_REPOSITORY_URI
BUILD_SOURCEBRANCH
BUILD_SOURCEVERSION
BUILD_SOURCEBRANCH
BUILD_SOURCEVERSION
SYSTEM_TEAMFOUNDATIONSERVERURI
SYSTEM_TEAMPROJECT
SYSTEM_JOBID
SYSTEM_TASKINSTANCEID
SYSTEM_PULLREQUEST_SOURCEREPOSITORYURI
SYSTEM_PULLREQUEST_SOURCEBRANCH
SYSTEM_PULLREQUEST_SOURCECOMMITID
Full list of build environment variables provided by Azure Pipelines