We'll probably need more context to understand your problem. As far as I know, prune stale remote-tracking branches is generally well-behaved, at least in the contexts where I test it.
Mark Waite On Tuesday, July 5, 2016 at 3:40:05 AM UTC-6, Marcelito de Guzman wrote: > > I have successfully integrated Jenkins with Github. I created multiple > branches and have deleted them, however, Jenkins is still seeing them when > building which causes it to fail. > > I've already deleted the branches on GitHub and set additional behaviors > on Jenkins like: > > Prune stale remote-tracking branches > > Clean before checkout > > Clean after checkout > > Looked at jenkins.log and there was a message about the account jenkins is > using not having admin access for webhooks but I've taken care of that by > giving the account admin access which is a bit risky in my opinion though, > so if anyone knows any workaround for this too i'd be more than glad to > hear it. > > So basically, now I'm having problems regarding Jenkins seeing the deleted > branches on GitHub. Anyone knows how to solve this one? > > > Cheers, > Marz > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/73695a98-2d24-4716-8752-62a304c4433c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
