Skip to content

GitLab

failed Pipeline #2659 triggered by
torgiren
@torgiren

Update .gitlab-ci.yml file

2 jobs for v0.3.1 in 35 seconds (queued for 1 second)
latest
9024dffc
No related merge requests found.
Status
Job
Stage
Name
Duration
Coverage
No jobs to show
Name Stage Failure
failed
deploy-to-dev Deploy 
E0404 05:05:36.143266      79 memcache.go:265] couldn't get current server API group list: Get "https://kube-dev.fabrykowski.pl/api?timeout=32s": dial tcp 31.179.32.96:443: connect: no route to host
E0404 05:05:39.260204      79 memcache.go:265] couldn't get current server API group list: Get "https://kube-dev.fabrykowski.pl/api?timeout=32s": dial tcp 31.179.32.96:443: connect: no route to host
E0404 05:05:42.395905      79 memcache.go:265] couldn't get current server API group list: Get "https://kube-dev.fabrykowski.pl/api?timeout=32s": dial tcp 31.179.32.96:443: connect: no route to host
E0404 05:05:45.525149      79 memcache.go:265] couldn't get current server API group list: Get "https://kube-dev.fabrykowski.pl/api?timeout=32s": dial tcp 31.179.32.96:443: connect: no route to host
Unable to connect to the server: dial tcp 31.179.32.96:443: connect: no route to host

Cleaning up project directory and file based variables

ERROR: Job failed: command terminated with 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