1879cf721c
Allows multiple reports per a patchset to be sent to pluggable destinations. These are configurable per pipeline and, if not specified, defaults to the legacy behaviour of reporting back only to gerrit. Having multiple reporting methods means only certain success/failure /start parameters will apply to certain reporters. Reporters are listed as keys under each of those actions. This means that each key under success/failure/start is a reporter and the dictionaries under those are sent to the reporter to deal with. Change-Id: I80d7539772e1485d5880132f22e55751b25ec198
38 lines
853 B
YAML
38 lines
853 B
YAML
includes:
|
|
- python-file: custom_functions_live_reconfiguration_functions.py
|
|
|
|
pipelines:
|
|
- name: gate
|
|
manager: DependentPipelineManager
|
|
failure-message: Build failed. For information on how to proceed, see http://wiki.example.org/Test_Failures
|
|
trigger:
|
|
gerrit:
|
|
- event: comment-added
|
|
approval:
|
|
- approved: 1
|
|
success:
|
|
gerrit:
|
|
verified: 2
|
|
submit: true
|
|
failure:
|
|
gerrit:
|
|
verified: -2
|
|
start:
|
|
gerrit:
|
|
verified: 0
|
|
precedence: high
|
|
|
|
jobs:
|
|
- name: ^.*-merge$
|
|
failure-message: Unable to merge change
|
|
hold-following-changes: true
|
|
- name: node-project-test1
|
|
parameter-function: select_debian_node
|
|
|
|
projects:
|
|
- name: org/node-project
|
|
gate:
|
|
- node-project-merge:
|
|
- node-project-test1
|
|
- node-project-test2
|