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

Dimension for VolumetricFlowRate added plus some tests

1 job for master in 3 minutes and 11 seconds
Status
Job
Stage
Name
Duration
Coverage
deploy
pages
00:03:11
Name
Stage
Failure
deploy
      [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :de.hftstuttgart.cityunits.tests
Cleaning up 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).

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.