-
Bug
-
Resolution: Unresolved
-
Critical
-
None
From looking at the code it seems that the maven pipeline plugin switched the dependency resolution to maven jobs to a new system using a jdbc database. As such when working in a mixed environment with both maven jobs and new jobs using the pipeline maven plugin, builds done using the pipeline maven plugin do not trigger maven jobs which depends on the artifact that was just built.
This leaves us with two options none of them are ideal:
1 switch all the maven pipeline jobs to DSL as maven jobs
2. switch all the dependent jobs to be pipeline jobs which involves many different steps.
Is there any plan to merge the two dependency resolution mechanisms so that they work together?