failed Pipeline #155820 triggered by
小 白蛋
@baidan

更新.gitlab-ci.yml文件

1 job for master in 2 seconds (queued for 7 seconds)
latest
Status
Job
Stage
Name
Duration
Coverage
sast
sast
00:00:02
Name
Stage
Failure
sast
      Running with gitlab-runner 15.5.0 (0d4137b8)
on 333b14764c1e dvVEjZHD

Resolving secrets
Preparing the "docker" executor
Using Docker executor with image repo.gitsec.cn/docker/ssp-command:latest ...
Pulling docker image repo.gitsec.cn/docker/ssp-command:latest ...

WARNING: Failed to pull image with policy "always": Error response from daemon: Get "https://repo.gitsec.cn/v2/": dial tcp: lookup repo.gitsec.cn on 100.125.136.29:53: no such host (manager.go:237:0s)
ERROR: Job failed: failed to pull image "repo.gitsec.cn/docker/ssp-command:latest" with specified policies [always]: Error response from daemon: Get "https://repo.gitsec.cn/v2/": dial tcp: lookup repo.gitsec.cn on 100.125.136.29:53: no such host (manager.go:237:0s)

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no test reports for this pipeline

You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.