Bug: Multiple automatic triggers occurring in a pipeline which is configured manual

[badal773]

📜 Description

Description: In a ci-pipeline, there's a manual configuration set up a long time back. However, we're now experiencing multiple automatic triggers with various branches, despite no recent commits. This unexpected behavior is causing confusion.

We're unable to identify the root cause of these triggers and need assistance in debugging this issue. Please let us know if any additional information is required from our end to resolve this issue effectively.

Affected areas

CI

Additional affected areas

None

Prod/Non-prod environments?

Prod

Is User unblocked?

Yes

How was the user un-blocked?

None

Impact on Enterprise

NA

👟 Steps to replicate the Issue

NA

👍 Expected behavior

NA

👎 Actual Behavior

NA

☸ Kubernetes version

1.26

Cloud provider

eks

🌍 Browser

Chrome

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

AB#9556

[github-actions]

Final Score: 100

[ShashwatDevtron]

The event is coming across multiple clusters and we are fetching the workflow Id on the basis of workflow name. Thus, triggering the build. For now we have set INCLUSTER mode. This also needs to be fixed from the code side.