...
The downstream property can be defined for a job to manually define dependencies. Typically it's not required as the Maven Jenkins plug-in automatically infers the dependencies from the pom.xml files. However, this is currently not supported for the provisioning model or for Pax-Exam dependencies included in Java files, as the Maven plugin is unaware of those dependencies. In that scenario, dependencies need to be declared manually. This can be worked around by setting the jobs to build daily, even if no changes are performed in SCM for that module, by setting the rebuildDaily property for that module to true. See
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Also note that if a job has manual dependencies and is built for multiple Java versions, only the first job will have declared dependencies. The reason is that only the first job will deploy artifacts, and creating dependencies for the second job will lead to useless job triggers.
...