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
..
common-config	Fix mixed canonical/non-canonical project merge	2017-11-29 20:34:06 +01:00
org_project1	Allow per-repo selection of configuration classes to load	2017-06-08 11:38:03 -07:00
org_project2	configloader: add variant-description	2018-04-12 03:11:13 +00:00
org_project3	Don't validate references for excluded config items	2018-05-03 09:58:02 +02:00