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 ...)
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cdc29a9c-01aa-4745-a558-39ed8ef730e3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
