Skip to content

Updating docker image checks to make sure JMX image available and used for pipelines #3564

Updating docker image checks to make sure JMX image available and used for pipelines

Updating docker image checks to make sure JMX image available and used for pipelines #3564

Triggered via pull request November 28, 2024 12:14
Status Failure
Total duration 5m 56s
Artifacts

lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 errors
lint-go: components/datadog/agent/docker.go#L49
not enough arguments in call to e.InternalRegistryFullImagePathExists
lint-go: resources/aws/ecs/fargateService.go#L13
could not import github.com/DataDog/test-infra-definitions/components/datadog/agent (-: # github.com/DataDog/test-infra-definitions/components/datadog/agent
lint-go: components/datadog/agent/docker.go#L49
not enough arguments in call to e.InternalRegistryFullImagePathExists
lint-go: scenarios/aws/ec2/vm_run.go#L7
could not import github.com/DataDog/test-infra-definitions/components/datadog/agent (-: # github.com/DataDog/test-infra-definitions/components/datadog/agent
lint-go: components/datadog/agent/docker.go#L49
not enough arguments in call to e.InternalRegistryFullImagePathExists
lint-go: scenarios/aws/ecs/run.go#L5
could not import github.com/DataDog/test-infra-definitions/components/datadog/agent (-: # github.com/DataDog/test-infra-definitions/components/datadog/agent
lint-go: components/datadog/agent/docker.go#L49
not enough arguments in call to e.InternalRegistryFullImagePathExists
lint-go
issues found