failed Pipeline #1637 triggered by
Kai-Holger Brassel
@brassel

Revert "No runner with tag "production" available."

41415399
3 jobs for master
Status
Job
Stage
Name
Duration
Coverage
deploy
pages-master
00:00:01
deploy
pages-master
00:00:03
deploy
pages-master
Name
Stage
Failure
deploy
      Fetching changes with git depth set to 50...
Reinitialized existing Git repository in /var/gitlab-runner-working-dir/builds/gCnQN1L7/0/gitlab/neqmodplus/indriya-p2/.git/
Checking out 7a4587c1 as master...
Skipping Git submodules setup
Executing "step_script" stage of the job script
$ mkdir "$EXPORT_DIR/$CI_PROJECT_NAME"
mkdir: cannot create directory ‘/var/www/html/pages/indriya-p2’: File exists
Cleaning up file based variables
ERROR: Job failed: exit status 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).

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.