Re: 4 month old deleted branches still not removed

2017-06-21 Thread Michael Neale
I think it is fine to expect some infrequent scanning - it probably needs to be the default though as otherwise people wire up a webhook - and end up never deleting branches. On Wednesday, June 21, 2017 at 6:49:02 PM UTC+10, Stephen Connolly wrote: > > On 21 June 2017 at 01:16, Michael Neale >

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Stephen Connolly
On 21 June 2017 at 01:16, Michael Neale wrote: > Mark do you have a scan interval set? > > Should the github events include removing of branch projects? as that > doesn't seem to be happening lately (since a few months). > So the multibranch API does not allow us to know if an event about a bran

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Michael Neale
Mark do you have a scan interval set? Should the github events include removing of branch projects? as that doesn't seem to be happening lately (since a few months). On Wednesday, June 21, 2017 at 6:13:32 PM UTC+10, Stephen Connolly wrote: > > > > On 21 June 2017 at 00:19, Michael Neale > wro

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Stephen Connolly
On 21 June 2017 at 01:04, Michael Neale wrote: > reading the docs for folders, perhaps there is a bug from a bad > assumption. a github event will not trigger a scan like the author of the > folders plugin implies so it still needs to have this set even for > github > Link to the docs please

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Stephen Connolly
On 21 June 2017 at 00:19, Michael Neale wrote: > > > On Wednesday, June 21, 2017 at 4:19:58 PM UTC+10, Stephen Connolly wrote: >> >> >> >>> >>> Periodic triggers >>> >>> you want "periodically unless otherwise run" to be something like once a >>> day/week depending on how long you can handle a mi

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Michael Neale
reading the docs for folders, perhaps there is a bug from a bad assumption. a github event will not trigger a scan like the author of the folders plugin implies so it still needs to have this set even for github On Wednesday, June 21, 2017 at 6:03:03 PM UTC+10, Michael Neale wrote: > > OK on

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Michael Neale
OK on looking further - MBPs created by classic don't have this set - which seems wrong - worthy of a ticket? Ones created by blue ocean do have it set (1 day, as it turns out) via the github org folder. So this explains it, but leaves the issue of the default for creation being wrong. to b

Re: 4 month old deleted branches still not removed

2017-06-21 Thread Michael Neale
On Wednesday, June 21, 2017 at 4:19:58 PM UTC+10, Stephen Connolly wrote: > > > >> >> Periodic triggers >> >> you want "periodically unless otherwise run" to be something like once a >> day/week depending on how long you can handle a missed event (which should >> be unlikely) >> >> I recommend

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Stephen Connolly
On Wed 21 Jun 2017 at 06:54, Michael Neale wrote: > > > On Wednesday, June 21, 2017 at 3:50:06 PM UTC+10, Stephen Connolly wrote: >> >> >> How often is a full scan? >> > > Is that is from the scan log link - then not for 2 months or so. What > triggers that? All the settings are stock. > Periodi

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Stephen Connolly
On Wed 21 Jun 2017 at 07:18, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On Wed 21 Jun 2017 at 06:54, Michael Neale wrote: > >> >> >> On Wednesday, June 21, 2017 at 3:50:06 PM UTC+10, Stephen Connolly wrote: >>> >>> >>> How often is a full scan? >>> >> >> Is that is from the scan

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Michael Neale
On Wednesday, June 21, 2017 at 3:50:06 PM UTC+10, Stephen Connolly wrote: > > > How often is a full scan? > Is that is from the scan log link - then not for 2 months or so. What triggers that? All the settings are stock. > > Orphaned items are only removed on a full scan. > > New items ar

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Stephen Connolly
On Wed 21 Jun 2017 at 06:17, Michael Neale wrote: > github? polling or webhooks? > > The "scan respotory log" doesn't show anything recent (but new branches > are still being built) - does yours show anything different? > How often is a full scan? Orphaned items are only removed on a full scan.

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Michael Neale
github? polling or webhooks? The "scan respotory log" doesn't show anything recent (but new branches are still being built) - does yours show anything different? This seems a recent thing (well a change in last few months) or else we would have > 4 month old dead branches. On Wednesday, 21

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Mark Waite
Correct. I have some test jobs which intentionally create and destroy branches as part of their testing, and those branches correctly disappear shortly after the branch deletion is detected. On Tue, Jun 20, 2017 at 8:34 PM Michael Neale wrote: > and obviously you aren't seeing deleted branches

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Michael Neale
and obviously you aren't seeing deleted branches still show up without being cleaned up? On Wednesday, June 21, 2017 at 12:23:59 PM UTC+10, Mark Waite wrote: > > Yes, that's how mine is configured. > > On Tue, Jun 20, 2017 at 8:21 PM Michael Neale > wrote: > >> Yes I suspected that - it is the

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Mark Waite
Yes, that's how mine is configured. On Tue, Jun 20, 2017 at 8:21 PM Michael Neale wrote: > Yes I suspected that - it is the default that you get when you create a > new project (see below screen shot). Is this is what yours is? > > This multibranch project has been around for a while - and it on

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Michael Neale
Yes I suspected that - it is the default that you get when you create a new project (see below screen shot). Is this is what yours is? This multibranch project has been around for a while - and it only recently started showing this behavior (recently as 4 months) so I suspect something changed

Re: 4 month old deleted branches still not removed

2017-06-20 Thread Mark Waite
There is a configuration setting, "Orphaned Item Strategy", in the multi-branch pipeline job definition and in the GitHub Organization Folders definition which sets a retention period for jobs associated with deleted branches. Mine is set to Discard old items, with a retention period of 0 days. I

4 month old deleted branches still not removed

2017-06-20 Thread Michael Neale
Using multibranch and git/github, I am seeing projects that are created for a branch be apparently marked for deletion, but never removed. There is one that hasn't been around for 4 months and shows up like this: