Re: Reg scanning for all branches in Multi branch pipeline

Hi Jan, Thank you for the reply. How would it know what branches have a jenkins file without scanning them all? -->> Yeah, it should scan to know initially. But in our case, for each PR targeted to specific branch also, it is scanning all branches. Can we avoid it ? Follow up question, why 450 b

Re: Reg scanning for all branches in Multi branch pipeline

Hi Jan, Thanks for reply. How would it know what branches have a jenkins file without scanning them all? -->> Exactly. For the first scan, I am fine with that. But for each PR, does it require to scan as my PR is targeted to specific branch.? Follow up question, why 450 branches? Are they all

Re: Reg scanning for all branches in Multi branch pipeline

Could you use one of those PruneStaleBranches traits? https://github.com/jenkinsci/git-plugin/blob/dd2b84217cc967bf908c7f2c02beea27973cd884/src/main/java/hudson/plugins/git/extensions/impl/PruneStaleBranch.java > Or can we add any rule like scan only branches which has Jenkinsfile How would i

Reg scanning for all branches in Multi branch pipeline

Hi, Greetings ! We are currently using Bitbucket + Jenkins. In our Bitbucket repo, we have around ~450 branches due to some old reasons. When we raise any Pull request, Jenkins automatically scanning all 450 branches which is taking time to finish build for Pull Request. This is happening for