Albin Vass c81c2c6eec Filter events on event connection ... Currently if two triggers of the same connection type need to trigger on different events it's not possible to do so since the events are never filtered on which connection they came from. For example with the following setup where gerrit-org-1 only wants to trigger on changes to 'master' and gerrit-org-2 only wants to trigger on changes to 'develop' they will instead both trigger on 'master' and 'develop'since the events are never filtered on which connection they came from. - pipeline: name: check trigger: gerrit-org-1: - event: patchset-created branch: 'master' gerrit-org-2: - event: patchset-created branch: 'develop' Change-Id: Ia0476d71dee59c8b80db7630ac7a524bce87e6f9		2021-04-24 08:39:03 -07:00
..
fixtures	Filter events on event connection	2021-04-24 08:39:03 -07:00
nodepool	Simplify ZooKeeper client initialization	2021-02-21 07:41:43 -08:00
remote	Prohibit invalid uri usages on localhost	2020-09-23 18:59:52 +00:00
unit	Filter events on event connection	2021-04-24 08:39:03 -07:00
zuul_client	Merge "zuul-client: test encryption of large secrets"	2021-01-29 02:17:55 +00:00
__init__.py	Add non-voting jobs.	2012-08-23 23:20:09 +00:00
base.py	Clarify merger updates and resets	2021-04-21 14:53:54 -07:00
encrypt_secret.py	Make tests' encrypt_secret.py work with python3	2017-10-19 18:09:57 +00:00
fake_graphql.py	Fetch can-merge info when updating a pull-request	2020-09-23 12:03:55 +02:00
fakegithub.py	Save superfluous api requests in check run reporting	2020-11-04 08:52:28 +01:00
make_playbooks.py	Use libyaml if possible	2017-04-04 11:49:05 -07:00
print_layout.py	Do not add implied branch matchers in project-templates	2017-09-30 10:19:07 -07:00