• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: multibranch-build-strategy-extension-plugin
• Labels:

  None

1. 

   image-2020-01-27-15-48-22-389.png

   30 kB

   2020-01-27 18:48

[JENKINS-60882] Build not being prevented to run when it is the first build of that branch

Felipe Santos created issue - 2020-01-27 18:51

Felipe Santos made changes - 2020-06-25 19:54

Description

Original: I have a filter like this:  !image-2020-01-27-15-48-22-389.png|width=823,height=210! sIf the build is the first build of a given branch OR a change request/PR, the build get triggered even if the conditions doesn't pass. On log I can see the following Matched included region:project-a/** with file path:project-a/Jenkinsfile But the PR doesn't have any change under project-a folder, but it still gets recognized as it have.

New: I have a filter like this:   !image-2020-01-27-15-48-22-389.png|width=823,height=210! If the build is the first build of a given branch OR a change request/PR, the build gets triggered even if the conditions don't pass. On the log, I can see the following  Matched included region:project-a/** with file path:project-a/Jenkinsfile But the PR doesn't have any change under project-a folder, and it still gets recognized as it has.