We are running Jenkins on a CentOS VM and our Jobs are all declarative Pipelines. We have jobs that produce mvn SNAPSHOT artifacts and jobs that produce mvn releases. All of the maven commands are executed within the Pipeline withMaven step and are therefore added to the dependency graph. For the SNAPSHOT jobs we have "Build whenever a SNAPSHOT dependency is built" activated. The release jobs are only triggered manually.

All this was working as expected when using our old Jenkins instance (2.138.3), but when moving to the new Jenkins this behaviour changed in some cases. What happens is that Jobs which have no trigger event configured at all are suddenly triggered with an upstream trigger cause. (see images) This is especially painful, because suddenly release jobs are triggered by snapshot jobs.

I cannot really state a reason for this or "this only happens when...." because I could not identify such a thing. It does not happen with all the Jobs, it also does not happen every time. The only thing I could recognize is that jobs which are triggered falsly are always of the type pipeline and jobs that are the cause of the trigger are sometimes Pipelines or Multibranch Project Pipelines.

As a workaround I added a step in the pipeline which checks the trigger cause and aborts the job, if it is not triggered manually, but this is very ugly and produces false results in our monitoring. 

It would really appreciate some help with this topic, or at least some clue on how to debug this. Thanks in advance!