initial release

3 jobs for master in 13 seconds (queued for 2 seconds)

Build

Test

Status	Name	Job ID
Build
failed	build	#1896	00:00:13 4 years ago

Test
skipped	code_quality	#1898 allowed to fail
skipped	test	#1897

Name Stage Failure

	Name	Stage	Failure
failed	build	Build
	`Checking out d81ef11a as master... Skipping Git submodules setup Executing "step_script" stage of the job script $ if [[ -z "$CI_COMMIT_TAG" ]]; then # collapsed multi-line command $ /build/build.sh Logging to GitLab Container Registry with CI credentials... error during connect: Post http://docker:2375/v1.40/auth: dial tcp: lookup docker on 1.1.1.1:53: no such host ERROR: Job failed: exit code 1`

failed

build

Build

Checking out d81ef11a as master...

Skipping Git submodules setup
Executing "step_script" stage of the job script
$ if [[ -z "$CI_COMMIT_TAG" ]]; then # collapsed multi-line command
$ /build/build.sh
Logging to GitLab Container Registry with CI credentials...
error during connect: Post http://docker:2375/v1.40/auth: dial tcp: lookup docker on 1.1.1.1:53: no such host
ERROR: Job failed: exit code 1

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).

Learn more about Needs relationships

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.

Learn how to upload pipeline test reports