I don't understand why one of my jobs starts another

[Erik Vande Velde]

We have 3 automatic builds every night: (1) trunk (2) release 2.0 (3) release 1.1.

These 3 builds are built up out of flows defined with the 'Build Flow Plugin'. Since a couple of days some jobs out of one build start triggering jobs from another build, and I don't understand why. I just see messages like 

...

Started by upstream project Fugris2.0_Toolbox_Build build number 77

originally caused by:

Started by upstream project FugrisTrunk_Util_Testing build number 1179

... 

So apparently a job in the trunk flow decided to start a job in the release 2.0 flow. How can i find out WHY jenkins thins that trunk_util wants to start 2.0_toolbox ?

The only workaround I see is to check 'disable triggering of downstream project' for each and every job (about 100 of them ...)

[Daniel Beck]

On 13.04.2016, at 09:39, Erik Vande Velde <vandeve...@gmail.com> wrote:

> How can i find out WHY jenkins thins that trunk_util wants to start 2.0_toolbox ?

Look at and/or provide the configuration of the job that does something you don't expect it to.

[Erik Vande Velde]

The config.xml of the upstream job is attached, there is no obvious reference to the other job ...