GerritTriggerSpec
The configurations of a Gerrit Trigger decides which pipeline is required to be triggered depending on kind of event received.
{
"branch": "master",
"configurations": [
{
"pipeline": "rest_pipeline",
"input": {},
"eventType": "change-merged",
"failureComment": "Pipeline Execution Failed",
"successComment": "Pipeline Execution Successful"
},
{
"pipeline": "rest_pipeline",
"input": {},
"eventType": "patchset-created",
"verifiedLabel": "Verified",
"failureComment": "Pipeline Failed",
"successComment": "Pipeline Completed"
}
],
"description": "string",
"enabled": true,
"exclusions": [
{
"type": "PLAIN",
"value": "example.txt"
}
],
"gerritProject": "TestGerritProject",
"inclusions": [
{
"type": "PLAIN",
"value": "example.txt"
}
],
"listener": "Gerrit-Listener",
"name": "My-Name",
"prioritizeExclusion": true,
"project": "My-Project"
}
Gerrit Project Branch on which the change has to be monitored.
The configuration of an Gerrit Event.
A human-friendly description.
Indicates that this trigger will be addressed on receiving respective events.
Provide file exclusions as conditions for the trigger.
Gerrit Project which is to be monitored for the change.
Provide file inclusions as conditions for the trigger.
Gerrit Listener which will receive the events for this trigger.
A human-friendly name used as an identifier in APIs that support this option
Prioritize Exclusion ensures that pipelines are not triggered even if any of the files in a commit match the specified files in the exclusion paths or regex.
The project this entity belongs to.