I think the point is to prevent an automatic build of a shedload of old pre-existing branches when creating a multi branch pipeline job for an older repo, even though from then onwards, you want new branches to be auto-discovered and built. Regexes can’t always help with this.
It’s not really an argument about whether repositories *should* be in that state, it’s that sometimes they are and you need to be able to work with them without crippling a Jenkins server for hours at a time when creating new jobs. Sent from my iPhone > On 18 Apr 2020, at 14:33, Jesse Glick <[email protected]> wrote: > > On Wed, Apr 15, 2020 at 9:11 AM Adam Gabryś <[email protected]> wrote: >> when people don't delete old branches > > FYI, for GitHub at least you can address this directly: > > https://help.github.com/en/github/administering-a-repository/managing-the-automatic-deletion-of-branches > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3bpVX4owimCtFYmjeg8-Wmh9L9nbY942JgtccP-xTVog%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/A3ED39F8-7309-4CE8-B1EB-1B2D303F8A7A%40gmail.com.
