Skip to content

GitLab

failed Pipeline #36134 triggered by
Lorenz Kapsner
@lorenz.kapsner

chore: cran version

6 jobs for v0.0.2 in 9 seconds (queued for 1 second)
latest
ccc33824
No related merge requests found.
Loading
Name Stage Failure
failed
build_new_base_image Get Base Image 
Using docker image sha256:456c635446977ad70607efd5889908b1ccb8b727ae6244dca0569b72c2b63ead for docker:git with digest docker@sha256:fe99b62ceb53a90c054c55e86440cf00d13b3ff2f3d99692a0bef4adc1b45c67 ...
$ echo ${R_BASE_IMAGE__REGISTRY_PASSWORD} | docker login -u ${R_BASE_IMAGE__REGISTRY_USERNAME} ${R_BASE_IMAGE__REGISTRY_URL} --password-stdin
Error: Cannot perform an interactive login from a non TTY device
Running after_script
Running after script...
$ docker logout ${R_BASE_IMAGE__REGISTRY_URL}
Removing login credentials for harbor.miracum.org
Cleaning up project directory and file based variables
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