Scan Repository Triggers project settings not taken into account by repositories

7 views
Skip to first unread message

Damien Coraboeuf

unread,
May 15, 2019, 8:26:30 AM5/15/19
to Jenkins Users
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 level.

Project level:


Repository level:


This is really a pain since this creates a surge of new builds every day, for very little use.

Thanks for any help,
Damien

Damien Coraboeuf

unread,
May 15, 2019, 9:42:20 AM5/15/19
to Jenkins Users
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
Reply all
Reply to author
Forward
0 new messages