Clint Byrum 5c9072e958 Don't validate references for excluded config items ... Because of the way the exclude options work in tenant project configs, we will still parse the job objects, even if we plan to discard them later. This leads to failed config loading if we validate references of config options we would exclude anyway. This can be fixed by moving the exclude filter into parseConfig where the parsed config (which is tenant specific) is generated. Co-Authored-By: Tobias Henkel <tobias.henkel@bmw.de> Change-Id: I78b68c5a3c8d403f0837d154a4ac47d11876bae5		2018-05-03 09:58:02 +02:00
..
git	Don't validate references for excluded config items	2018-05-03 09:58:02 +02:00
groups.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
groups2.yaml	Don't validate references for excluded config items	2018-05-03 09:58:02 +02:00
groups3.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
groups4.yaml	Do not call merger:cat when all config items are excluded	2018-02-07 12:12:25 +01:00
override.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
simple.yaml	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
tenant_config_script.py	Tenant config can be read from an external script	2018-04-03 14:33:41 +02:00
unprotected-branches.yaml	Optionally limit github to protected branches	2017-08-03 11:50:26 +02:00