Skip to content

GitLab

An error occurred while fetching the pipelines jobs.
failed Pipeline #11081 triggered by
Bruno da Silva Castilho
@bruno.s.c

Transformação para base64 é feito no front-end

2 jobs for main in 2 minutes and 50 seconds (queued for 1 second)
latest
0d8ce97d
No related merge requests found.
Status
Job
Stage
Name
Duration
Coverage
No jobs to show
Name Stage Failure
failed
portainer Portainer 
Reinitialized existing Git repository in /builds/setic-hpc/webqueue/slurm-api/.git/
Skipping Git checkout
Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:b0757c55a1fdbb59c378fd34dde3e12bd25f68094dd69546cf5ca00ddbaa7a33 for docker:stable with digest docker@sha256:fd4d028713fd05a1fb896412805daed82c4a0cc84331d8dad00cb596d7ce3e3a ...
$ if [[ ! -z "${WEBHOOK_PORTAINER}" ]]; then for url in $(echo ${WEBHOOK_PORTAINER} | sed "s/,/ /g"); do wget --post-data '' -O - "$url"; done else echo "Empty \$WEBHOOK_PORTAINER" ; exit 1; fi
Empty $WEBHOOK_PORTAINER
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