Jenkins pipeline triggered without no changed files

Using Jenkins
1

Hi Team,

We have configured a Jenkins pipeline with an SCM poll option. The pipeline is configured to trigger a build if a file is changed on a particular directory. We are facing a strange issue with the build getting triggered when a PR is merged without any file changes. One of the dev team members created two PR with some modifications to the same file, once the first PR was merged, the second PR didn’t show any file changes but the pipeline got triggered when the second PR was merged. How can we avoid the second build?

Regards,
Aravind

2

Hello @ambadiaravind and welcome to this community :wave:

Would you have any logs to share?
Could you please show us your configuration?

Thanks.