Essentially just that there isnt disagreement about wiping it all
(since it means some ancient stuff will go, and current stuff will be
'missing' for a small time until created again).

Not unreasonable...besides, it's been a mess for several years, a
couple days for gauging consensus doesn't really hurt hehe.

It seems perhaps someone has been cleaning a little already though,
perhaps tweaking the version-was-released cleanup, as some of the
effectively-nothing-there junk within the wider clutter actually seems
to have disappeared already.

On Wed, 2 Aug 2023 at 15:48, Clebert Suconic <clebert.suco...@gmail.com> wrote:
>
> I’m just saying it should be a no brainer.   Old stuff on snapshot can go.
>
> I’m not sure what consensus infra is asking on the JIRA.
>
> On Tue, Aug 1, 2023 at 10:12 AM Robbie Gemmell <robbie.gemm...@gmail.com>
> wrote:
>
> > Yep, committers can also manually do a deploy.
> >
> > Old snapshots are removed when the 'matching non-snapshot version' is
> > released. Though it does still leave behind some metadata, so the
> > related folders typically still all remain, making it a little harder
> > to see what really is there. There are lots of these in the tree.
> >
> > Things that never actually get released for a variety of reasons
> > currently stick around forever (e.g as the component was never
> > actually released again, or a specific module went away before
> > release, or the version number was changed between initial development
> > and the eventual release, etc etc). There are also a variety of these
> > in the tree as well.
> >
> > On Tue, 1 Aug 2023 at 14:40, Clebert Suconic <clebert.suco...@gmail.com>
> > wrote:
> > >
> > > +1000
> > >
> > > the snapshot can also be deployed by anyone's laptop from a PMC member.
> > >
> > >
> > >
> > > I thought there was an automatic rule to remove snapshots from ages
> > > ago already. IMO This should be a no brainer on removing anything that
> > > was deployed more than 3 months ago.
> > >
> > >
> > > if we need to wipe it clean and redeploy all current snapshots that
> > > may be a good way to clean it up...
> > >
> > > the best way would be to have a rule removing any component (or
> > > version) that didn't have an upload in more than 3 months.
> > >
> > > On Mon, Jul 31, 2023 at 1:41 PM Robbie Gemmell <robbie.gemm...@gmail.com>
> > wrote:
> > > >
> > > > The jobs set up on Jenkins do it, either as part of an overall build
> > > > job or specifically just for snapshots.
> > > >
> > > > The various branch specific 5.x jobs do it as part of their overall
> > > > process, they are under:
> > > > https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ/
> > > >
> > > > For Artemis there is just a specific snapshot deploy job for main at:
> > > >
> > https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ-Artemis-SNAPSHOT-Deploy/
> > > >
> > > > On Mon, 31 Jul 2023 at 18:07, Justin Bertram <jbert...@apache.org>
> > wrote:
> > > > >
> > > > > I have no objections, but I do have a question. What is pushing those
> > > > > snapshots?
> > > > >
> > > > >
> > > > > Justin
> > > > >
> > > > > On Mon, Jul 31, 2023 at 12:02 PM Robbie Gemmell <
> > robbie.gemm...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Infra have said they would be happier with PMC consensus first for
> > a
> > > > > > bulk clear (which I suggested as picking out individual stuff to
> > clear
> > > > > > or keep would be a nightmare), so lets go with a lazy consensus
> > poll:
> > > > > >
> > > > > > Does anyone object to bulk-clearing of the stale contents of the
> > > > > > snapshot repo, and having the CI jobs repopulating only fresh
> > stuff?
> > > > > >
> > > > > > Lets say lazy consensus will be assumed on Friday failing
> > discussion
> > > > > > otherwise.
> > > > > >
> > > > > > Robbie
> > > > > >
> > > > > > On Mon, 31 Jul 2023 at 12:05, Robbie Gemmell <
> > robbie.gemm...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Hi folks, just a note that I have raised a JIRA to ask Infra to
> > clear
> > > > > > > out the snapshots repo, as I came to realise it is full of a
> > > > > > > considerable amount of stale junk, including things that either
> > add
> > > > > > > clutter or just actively mislead people. Once cleared the
> > nightly jobs
> > > > > > > can then deploy just the stuff currently being worked on.
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/INFRA-24848
> > > > > >
> > > > > >
> > >
> > >
> > >
> > > --
> > > Clebert Suconic
> >
> --
> Clebert Suconic

Reply via email to