You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the build of optimize-backend module, the spring boot artifacts are not fetched properly. The following warnings can be found in the logs:
Logs[WARNING] The POM for org.springframework.boot:spring-boot-starter:jar:${spring-boot.version} is missing, no dependency information available
[WARNING] The POM for org.springframework.boot:spring-boot-starter-web:jar:${spring-boot.version} is missing, no dependency information available
[WARNING] The POM for org.springframework.boot:spring-boot:jar:${spring-boot.version} is missing, no dependency information available
[WARNING] The POM for org.yaml:snakeyaml:jar:${snakeyaml.version} is missing, no dependency information available
[WARNING] The POM for org.springframework.boot:spring-boot-autoconfigure:jar:${spring-boot.version} is missing, no dependency information available
Note: The local build gets the artifact fetch misses from Nexus but does not fail; failure occurs only at the CI job.
Expected behavior (Required on creation)
The Run Java Checks job passes for PRs
Root Cause (Required on prioritization)
Solution Ideas
Hints
spring-boot.version property is reported in the logs but does not belong to optimize; spring.boot.version is used instead
Environment (Required on creation)
CI
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
The Run Java Checks job is Failing on PR builds
Steps to reproduce (Required on creation)
The issue can be reproduced consistently in two different ways:
master
cd camunda-optimize/optimize
from the projects rootmvn spotless:apply
mvn -T1C -B -DskipTests -P '!autoFormat,checkFormat' verify
Observed Behavior (Required on creation)
During the build of
optimize-backend
module, the spring boot artifacts are not fetched properly. The following warnings can be found in the logs:Logs
[WARNING] The POM for org.springframework.boot:spring-boot-starter:jar:${spring-boot.version} is missing, no dependency information available [WARNING] The POM for org.springframework.boot:spring-boot-starter-web:jar:${spring-boot.version} is missing, no dependency information available [WARNING] The POM for org.springframework.boot:spring-boot:jar:${spring-boot.version} is missing, no dependency information available [WARNING] The POM for org.yaml:snakeyaml:jar:${snakeyaml.version} is missing, no dependency information available [WARNING] The POM for org.springframework.boot:spring-boot-autoconfigure:jar:${spring-boot.version} is missing, no dependency information available
Note: The local build gets the artifact fetch misses from Nexus but does not fail; failure occurs only at the CI job.
Expected behavior (Required on creation)
The Run Java Checks job passes for PRs
Root Cause (Required on prioritization)
Solution Ideas
Hints
spring-boot.version
property is reported in the logs but does not belong to optimize; spring.boot.version is used insteadspring-boot.version
master
, only on PR buildsLinks
Breakdown
Pull Requests
Dev2QA handover
The text was updated successfully, but these errors were encountered: