An error occurred while fetching the pipelines jobs.

fixing teamplate jdbc

1 job for hotfix/exams in 4 minutes and 1 second (queued for 3 seconds)

Status	Job	Stage	Name	Duration	Coverage
No jobs to show

Name Stage Failure

	Name	Stage	Failure
failed	build-job	Build Test
	`You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 3m 19s 10 actionable tasks: 10 executed Cleaning up project directory and file based variables ERROR: Job failed: exit code 1`

failed

build-job

Build Test


You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.2.1/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 3m 19s
10 actionable tasks: 10 executed
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

GitLab

fixing teamplate jdbc

Speed up your pipelines with Needs relationships

Menu