release/6.0.0

Master

We start building the Release-Branches with Jenkins 2 or 3 weeks before the release. Just because we need this for the QA to get the automated Reports from Checkstyle Findbugs, sonarQube etc. (I know we have the data from the feature branches (and master), but that's what the QA wants.)

rpaasche I didn't catch that the Maven Tab didn't show the list of "produced maven artifacts". Can you please also tell us what is the produced artefact that causes this infinite loop?

Do you think that you could reproduce with a simplified test case that you could share on github?

I can't provide more details, I had to cut "produced maven artifacts" off. But its a simple Maven Project with 2 jars (as modules) where jar2 depends on jar1. These jars contains mostly Pojo and a view jaxb-classes. So nothing fancy.

But after downgrading to version 3.5.6 we see the following line in the log again (and no triggering):
[withMaven] Not triggering Sportec » sharedsources » master because it has dependencies in the downstream project list
Instead of:
[withMaven] Scheduling downstream pipeline Sportec » sharedsources » master#209...

So it sounds like a regression, correct? We have made some optimisations in the algorithm to identify the downstream pipelines to trigger, there may be a glitch here.

Correct it sounds like a regression.

rpaasche Your problem is hard to reproduce. Can you please test https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-51680
and add comments on https://github.com/jenkinsci/pipeline-maven-plugin/pull/155

Fixed in 3.5.10

looks like this create  regression where my downstream jobs are skipped with the bellow message in jenkins console log

[withMaven] Not triggering [x » y » z » master] because it has dependencies in the downstream project list

what does it mean?

Fixed in 3.5.12-beta-2