Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
270 changes: 0 additions & 270 deletions .github/workflows/reverse-sync.yml

This file was deleted.

8 changes: 4 additions & 4 deletions docs/en/triggers/trouble_shooting/pipeline_not_triggered.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ weight: 10

## Problem Description

After creating the `Pipeline` and `Trigger` using `Pipelines` functionality through the UI console, the `Pipeline` is not automatically triggered event though the event is sent (i.e the code is pushed).
After creating the `Pipeline` and `Trigger` using `Pipelines` functionality through the UI console, the `Pipeline` is not automatically triggered even though the event is sent (i.e the code is pushed).

## Root Cause Analysis

Expand All @@ -22,14 +22,14 @@ There are several possible causes for this issue:

Given the possible issues mentioned above, follow the steps to find the root cause of the problem:

### Webhook configuration was not setup correctly
### Webhook configuration was not set up correctly

1. Access your repository/settings using an account with appropriate permissions.
2. Check all webhook settings and confirm with the platform administrator details regarding the target address of the webhook.
3. Make sure the required events are enabled by the webhook. For Gitlab events please refer to [GitLab Event Triggers](../how_to/gitlab_events.mdx)
3. Make sure the required events are enabled by the webhook. For Gitlab events, please refer to [GitLab Event Triggers](../how_to/gitlab_events.mdx)


### EventLister not deployed or setup incorrectly
### EventListener not deployed or set up incorrectly

1. Verify with the Platform Administrator that the `EventListener` was deployed and can be reached from the event source (i.e Gitlab instance).
2. Access the `EventListener` resource and check if it is listening `Triggers` in the target namespace checking the `EventListener` resource `spec`, it should have the `namespaceSelector` field set to `*` or listing the target namespace.
Expand Down