Re: Scan Repository Triggers project settings not taken into account by repositories

Hi, resolved (while writing the post). One has to look at "Child Scan Triggers" at parent level - not at "Scan Organization Folder Triggers" BR Damien On Wednesday, 15 May 2019 14:26:30 UTC+2, Damien Coraboeuf wrote: > > Hi, > > We're using Jenkins 2.164.3, with the latest version of all our p

Scan Repository Triggers project settings not taken into account by repositories

Hi, We're using Jenkins 2.164.3, with the latest version of all our plugins. Everything is driven by SCM events (GitHub or Bitbucket server). We'd like very much to disable the "Branch indexing" - we've indeed done it at project folder level, but this settings is not propagated at repository l