-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Our standard is to build a SpringBoot fatjar containing one micro service, and then a docker image of it.
We use the [dockerfile-maven-plugin|https://github.com/spotify/dockerfile-maven] for the last part, and in particular its docker-info jars to record maven dependencies between images.
But these dependencies are not seen by the plugin, and thus dependent builds are not triggered.
The bad thing is :
- the docker-info jar, when produced, is recorded with type=docker-info and classifier=docker-info
- when consumed as a dependency, it is with type=jar and classifier=docker-info (even if forcing the type in the POM)
- relates to
-
JENKINS-50099 Downstream pipelines are not triggered when the artifact is a a WAR and consumed by war-overlay
- Open
-
JENKINS-50205 "runtime" scope dependencies are not tracked
- Open
-
JENKINS-50475 Scope import / Maven BOM dependencies
- Open
- links to