I have multiple Jenkins Jobs built using Maven:
Job 1: Builds WebApp and deploys war to artifactory
Job 2: Builds Core and deploys jar to artifactory
WebApp has a dependency on Core.
Is it possible for Jenkins to parse the POM, see that WebApp has this dependency on Core and thus triggers Job 2 before building WebApp? This would ensure WebApp uses an up-to-date, latest Core.jar
I can achieve this mechanism via the Jenkins Parameterized Trigger plugin's Pre-Steps feature but I would ideally like to handle this from the POM.
Thanks.
Yes there is.
Apparently this only works, if the dependency is a snapshot dependency.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With