You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Timothy Bish <ta...@gmail.com> on 2016/01/18 16:53:17 UTC
[DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
We seem to have a bit of a mess in our snapshots area with lots of old
snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
for an ActiveMQ 6.0.0 release that has caused some confusion recently.
Some examples of old snapshots or snapshot to things that were never
released.
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
We can request that infra wipe out the snapshots area and let the
jenkins runs repopulate with only the current builds for active project
work. Alternatively we can go through every folder and audit them but
given they are snapshots it's simpler just to blow them all away.
Thoughts?
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
+1
On Mon, Jan 18, 2016 at 10:53 AM, Timothy Bish <ta...@gmail.com> wrote:
> We seem to have a bit of a mess in our snapshots area with lots of old
> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>
> Some examples of old snapshots or snapshot to things that were never
> released.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>
> We can request that infra wipe out the snapshots area and let the
> jenkins runs repopulate with only the current builds for active project
> work. Alternatively we can go through every folder and audit them but
> given they are snapshots it's simpler just to blow them all away.
>
> Thoughts?
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Jim Gomes <e....@gmail.com>.
+1 for auto-removing the SNAPSHOTS of old projects.
On Mon, Jan 18, 2016 at 8:01 AM, Christopher Shannon <
christopher.l.shannon@gmail.com> wrote:
> +1 to blow away the snapshots area. I don't see any reason to keep around
> old snapshots of versions that were released and if they are not going to
> be released they should not be there.
>
> On Mon, Jan 18, 2016 at 10:53 AM, Timothy Bish <ta...@gmail.com>
> wrote:
>
> > We seem to have a bit of a mess in our snapshots area with lots of old
> > snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
> > for an ActiveMQ 6.0.0 release that has caused some confusion recently.
> >
> > Some examples of old snapshots or snapshot to things that were never
> > released.
> >
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
> >
> >
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
> >
> > We can request that infra wipe out the snapshots area and let the
> > jenkins runs repopulate with only the current builds for active project
> > work. Alternatively we can go through every folder and audit them but
> > given they are snapshots it's simpler just to blow them all away.
> >
> > Thoughts?
> >
> > --
> > Tim Bish
> > twitter: @tabish121
> > blog: http://timbish.blogspot.com/
> >
> >
> >
>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Christopher Shannon <ch...@gmail.com>.
+1 to blow away the snapshots area. I don't see any reason to keep around
old snapshots of versions that were released and if they are not going to
be released they should not be there.
On Mon, Jan 18, 2016 at 10:53 AM, Timothy Bish <ta...@gmail.com> wrote:
> We seem to have a bit of a mess in our snapshots area with lots of old
> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>
> Some examples of old snapshots or snapshot to things that were never
> released.
>
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>
> We can request that infra wipe out the snapshots area and let the
> jenkins runs repopulate with only the current builds for active project
> work. Alternatively we can go through every folder and audit them but
> given they are snapshots it's simpler just to blow them all away.
>
> Thoughts?
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
I thought you meant literally.. because next time we make a release we
would bump to 1.4.0-snapshot and these would be left unattended there.
that's why I thought you meant that.
On Wed, Jan 20, 2016 at 9:59 AM, Christopher Shannon
<ch...@gmail.com> wrote:
> I didn't mean X.X.0-SNAPSHOT literally...I was just using X as a version
> placeholder for whatever the current version is. For your version it would
> still be 1.2.1-SNAPSHOT or 1.3.0-SNAPSHOT, etc.
>
> On Wed, Jan 20, 2016 at 9:48 AM, Clebert Suconic <cl...@gmail.com>
> wrote:
>
>> Will that look ok?
>>
>> https://github.com/apache/activemq-artemis/pull/330
>>
>> On Wed, Jan 20, 2016 at 9:44 AM, Clebert Suconic
>> <cl...@gmail.com> wrote:
>> > We can do the same on Artemis....
>> >
>> > So it will be better to make the changes before cleaning up the repo
>> then.
>> >
>> > On Wed, Jan 20, 2016 at 7:26 AM, Christopher Shannon
>> > <ch...@gmail.com> wrote:
>> >> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>> >> X.X-SNAPSHOT for development versions so this makes sense to me.
>> >>
>> >> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has
>> any
>> >> complaints.
>> >>
>> >> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com>
>> wrote:
>> >>
>> >>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>> >>> > On 18 January 2016 at 18:46, Robbie Gemmell <
>> robbie.gemmell@gmail.com>
>> >>> wrote:
>> >>> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com>
>> wrote:
>> >>> >>> We seem to have a bit of a mess in our snapshots area with lots of
>> old
>> >>> >>> snapshots for ancient releases like 5.3, 5.4, etc along with
>> snapshots
>> >>> >>> for an ActiveMQ 6.0.0 release that has caused some confusion
>> recently.
>> >>> >>>
>> >>> >>> Some examples of old snapshots or snapshot to things that were
>> never
>> >>> >>> released.
>> >>> >>>
>> >>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>> >>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>> >>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>> >>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>> >>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>> >>> >>>
>> >>> >>> We can request that infra wipe out the snapshots area and let the
>> >>> >>> jenkins runs repopulate with only the current builds for active
>> project
>> >>> >>> work. Alternatively we can go through every folder and audit them
>> but
>> >>> >>> given they are snapshots it's simpler just to blow them all away.
>> >>> >>>
>> >>> >>> Thoughts?
>> >>> >>>
>> >>> >>> --
>> >>> >>> Tim Bish
>> >>> >>> twitter: @tabish121
>> >>> >>> blog: http://timbish.blogspot.com/
>> >>> >>>
>> >>> >>>
>> >>> >> Cleaning things up would definitely be good. Given the sizable
>> amount
>> >>> >> of cruft I dont think it makes sense to try pruning them
>> individually,
>> >>> >> and I'm not sure infra would be particularly happy at being asked
>> that
>> >>> >> either hehe, so the full wipe seems like the way to go to me.
>> >>> >>
>> >>> >> Robbie
>> >>> >
>> >>> > To add to that...
>> >>> >
>> >>> > Old snapshots normally get cleaned up once a release occurs but this
>> >>> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
>> >>> > bits are still there. The reason is likely that the snapshot versions
>> >>> > dont align with the end release version used, as the snapshots are
>> >>> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>> >>> > so the cleanup process isn't able to recognise that the snapshots
>> have
>> >>> > become stale artifacts following a release.
>> >>> >
>> >>> > We should probably also change to using 5.X.0-SNAPSHOT on master
>> >>> > (before asking infra to nuke the snapshot repo) to prevent more cruft
>> >>> > accumulating again with each future release.
>> >>> >
>> >>> > Robbie
>> >>> >
>> >>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>> >>> me some work Robbie :)
>> >>>
>> >>> --
>> >>> Tim Bish
>> >>> twitter: @tabish121
>> >>> blog: http://timbish.blogspot.com/
>> >>>
>> >>>
>> >
>> >
>> >
>> > --
>> > Clebert Suconic
>>
>>
>>
>> --
>> Clebert Suconic
>>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Christopher Shannon <ch...@gmail.com>.
I didn't mean X.X.0-SNAPSHOT literally...I was just using X as a version
placeholder for whatever the current version is. For your version it would
still be 1.2.1-SNAPSHOT or 1.3.0-SNAPSHOT, etc.
On Wed, Jan 20, 2016 at 9:48 AM, Clebert Suconic <cl...@gmail.com>
wrote:
> Will that look ok?
>
> https://github.com/apache/activemq-artemis/pull/330
>
> On Wed, Jan 20, 2016 at 9:44 AM, Clebert Suconic
> <cl...@gmail.com> wrote:
> > We can do the same on Artemis....
> >
> > So it will be better to make the changes before cleaning up the repo
> then.
> >
> > On Wed, Jan 20, 2016 at 7:26 AM, Christopher Shannon
> > <ch...@gmail.com> wrote:
> >> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
> >> X.X-SNAPSHOT for development versions so this makes sense to me.
> >>
> >> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has
> any
> >> complaints.
> >>
> >> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com>
> wrote:
> >>
> >>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
> >>> > On 18 January 2016 at 18:46, Robbie Gemmell <
> robbie.gemmell@gmail.com>
> >>> wrote:
> >>> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com>
> wrote:
> >>> >>> We seem to have a bit of a mess in our snapshots area with lots of
> old
> >>> >>> snapshots for ancient releases like 5.3, 5.4, etc along with
> snapshots
> >>> >>> for an ActiveMQ 6.0.0 release that has caused some confusion
> recently.
> >>> >>>
> >>> >>> Some examples of old snapshots or snapshot to things that were
> never
> >>> >>> released.
> >>> >>>
> >>> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
> >>> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
> >>> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
> >>> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
> >>> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
> >>> >>>
> >>> >>> We can request that infra wipe out the snapshots area and let the
> >>> >>> jenkins runs repopulate with only the current builds for active
> project
> >>> >>> work. Alternatively we can go through every folder and audit them
> but
> >>> >>> given they are snapshots it's simpler just to blow them all away.
> >>> >>>
> >>> >>> Thoughts?
> >>> >>>
> >>> >>> --
> >>> >>> Tim Bish
> >>> >>> twitter: @tabish121
> >>> >>> blog: http://timbish.blogspot.com/
> >>> >>>
> >>> >>>
> >>> >> Cleaning things up would definitely be good. Given the sizable
> amount
> >>> >> of cruft I dont think it makes sense to try pruning them
> individually,
> >>> >> and I'm not sure infra would be particularly happy at being asked
> that
> >>> >> either hehe, so the full wipe seems like the way to go to me.
> >>> >>
> >>> >> Robbie
> >>> >
> >>> > To add to that...
> >>> >
> >>> > Old snapshots normally get cleaned up once a release occurs but this
> >>> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
> >>> > bits are still there. The reason is likely that the snapshot versions
> >>> > dont align with the end release version used, as the snapshots are
> >>> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
> >>> > so the cleanup process isn't able to recognise that the snapshots
> have
> >>> > become stale artifacts following a release.
> >>> >
> >>> > We should probably also change to using 5.X.0-SNAPSHOT on master
> >>> > (before asking infra to nuke the snapshot repo) to prevent more cruft
> >>> > accumulating again with each future release.
> >>> >
> >>> > Robbie
> >>> >
> >>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
> >>> me some work Robbie :)
> >>>
> >>> --
> >>> Tim Bish
> >>> twitter: @tabish121
> >>> blog: http://timbish.blogspot.com/
> >>>
> >>>
> >
> >
> >
> > --
> > Clebert Suconic
>
>
>
> --
> Clebert Suconic
>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
The current format of the Artemis version on master (1.2.1-SNAPSHOT)
is fine. The only issue with it as a version would be if you dont
actually release 1.2.1, as then the snapshots wont get cleaned up
automatically. Given that the point releases didnt occur for 1.0.1 or
1.1.1 the obvious change would be to make master 1.3.0-SNAPSHOT now,
then 1.4.0-SNAPSHOT, etc etc. You can always still release a 1.X.1
straight from master regardless if desired (or make a branch).
The problem with the other old artifacts was that the modules were
renamed, from activemq-foo to artemis-foo, and reversioned from 6.0.0
to 1.0.0, so those old snapshots never got cleaned up as nothing
matching them ever appeared to be released.
Robbie
On 20 January 2016 at 14:48, Clebert Suconic <cl...@gmail.com> wrote:
> Will that look ok?
>
> https://github.com/apache/activemq-artemis/pull/330
>
> On Wed, Jan 20, 2016 at 9:44 AM, Clebert Suconic
> <cl...@gmail.com> wrote:
>> We can do the same on Artemis....
>>
>> So it will be better to make the changes before cleaning up the repo then.
>>
>> On Wed, Jan 20, 2016 at 7:26 AM, Christopher Shannon
>> <ch...@gmail.com> wrote:
>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>
>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>> complaints.
>>>
>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>
>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>> > On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>> wrote:
>>>> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>> >>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>> >>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>> >>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>> >>>
>>>> >>> Some examples of old snapshots or snapshot to things that were never
>>>> >>> released.
>>>> >>>
>>>> >>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>> >>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>> >>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>> >>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>> >>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>> >>>
>>>> >>> We can request that infra wipe out the snapshots area and let the
>>>> >>> jenkins runs repopulate with only the current builds for active project
>>>> >>> work. Alternatively we can go through every folder and audit them but
>>>> >>> given they are snapshots it's simpler just to blow them all away.
>>>> >>>
>>>> >>> Thoughts?
>>>> >>>
>>>> >>> --
>>>> >>> Tim Bish
>>>> >>> twitter: @tabish121
>>>> >>> blog: http://timbish.blogspot.com/
>>>> >>>
>>>> >>>
>>>> >> Cleaning things up would definitely be good. Given the sizable amount
>>>> >> of cruft I dont think it makes sense to try pruning them individually,
>>>> >> and I'm not sure infra would be particularly happy at being asked that
>>>> >> either hehe, so the full wipe seems like the way to go to me.
>>>> >>
>>>> >> Robbie
>>>> >
>>>> > To add to that...
>>>> >
>>>> > Old snapshots normally get cleaned up once a release occurs but this
>>>> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>> > bits are still there. The reason is likely that the snapshot versions
>>>> > dont align with the end release version used, as the snapshots are
>>>> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>> > so the cleanup process isn't able to recognise that the snapshots have
>>>> > become stale artifacts following a release.
>>>> >
>>>> > We should probably also change to using 5.X.0-SNAPSHOT on master
>>>> > (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>> > accumulating again with each future release.
>>>> >
>>>> > Robbie
>>>> >
>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>> me some work Robbie :)
>>>>
>>>> --
>>>> Tim Bish
>>>> twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>>>>
>>
>>
>>
>> --
>> Clebert Suconic
>
>
>
> --
> Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
Will that look ok?
https://github.com/apache/activemq-artemis/pull/330
On Wed, Jan 20, 2016 at 9:44 AM, Clebert Suconic
<cl...@gmail.com> wrote:
> We can do the same on Artemis....
>
> So it will be better to make the changes before cleaning up the repo then.
>
> On Wed, Jan 20, 2016 at 7:26 AM, Christopher Shannon
> <ch...@gmail.com> wrote:
>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>
>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>> complaints.
>>
>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>
>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>> > On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>> wrote:
>>> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>> >>> We seem to have a bit of a mess in our snapshots area with lots of old
>>> >>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>> >>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>> >>>
>>> >>> Some examples of old snapshots or snapshot to things that were never
>>> >>> released.
>>> >>>
>>> >>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>> >>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>> >>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>> >>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>> >>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>> >>>
>>> >>> We can request that infra wipe out the snapshots area and let the
>>> >>> jenkins runs repopulate with only the current builds for active project
>>> >>> work. Alternatively we can go through every folder and audit them but
>>> >>> given they are snapshots it's simpler just to blow them all away.
>>> >>>
>>> >>> Thoughts?
>>> >>>
>>> >>> --
>>> >>> Tim Bish
>>> >>> twitter: @tabish121
>>> >>> blog: http://timbish.blogspot.com/
>>> >>>
>>> >>>
>>> >> Cleaning things up would definitely be good. Given the sizable amount
>>> >> of cruft I dont think it makes sense to try pruning them individually,
>>> >> and I'm not sure infra would be particularly happy at being asked that
>>> >> either hehe, so the full wipe seems like the way to go to me.
>>> >>
>>> >> Robbie
>>> >
>>> > To add to that...
>>> >
>>> > Old snapshots normally get cleaned up once a release occurs but this
>>> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>> > bits are still there. The reason is likely that the snapshot versions
>>> > dont align with the end release version used, as the snapshots are
>>> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>> > so the cleanup process isn't able to recognise that the snapshots have
>>> > become stale artifacts following a release.
>>> >
>>> > We should probably also change to using 5.X.0-SNAPSHOT on master
>>> > (before asking infra to nuke the snapshot repo) to prevent more cruft
>>> > accumulating again with each future release.
>>> >
>>> > Robbie
>>> >
>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>> me some work Robbie :)
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
>>>
>
>
>
> --
> Clebert Suconic
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
We can do the same on Artemis....
So it will be better to make the changes before cleaning up the repo then.
On Wed, Jan 20, 2016 at 7:26 AM, Christopher Shannon
<ch...@gmail.com> wrote:
> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
> X.X-SNAPSHOT for development versions so this makes sense to me.
>
> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
> complaints.
>
> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>
>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>> > On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>> wrote:
>> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>> >>> We seem to have a bit of a mess in our snapshots area with lots of old
>> >>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>> >>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>> >>>
>> >>> Some examples of old snapshots or snapshot to things that were never
>> >>> released.
>> >>>
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>> >>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>> >>>
>> >>> We can request that infra wipe out the snapshots area and let the
>> >>> jenkins runs repopulate with only the current builds for active project
>> >>> work. Alternatively we can go through every folder and audit them but
>> >>> given they are snapshots it's simpler just to blow them all away.
>> >>>
>> >>> Thoughts?
>> >>>
>> >>> --
>> >>> Tim Bish
>> >>> twitter: @tabish121
>> >>> blog: http://timbish.blogspot.com/
>> >>>
>> >>>
>> >> Cleaning things up would definitely be good. Given the sizable amount
>> >> of cruft I dont think it makes sense to try pruning them individually,
>> >> and I'm not sure infra would be particularly happy at being asked that
>> >> either hehe, so the full wipe seems like the way to go to me.
>> >>
>> >> Robbie
>> >
>> > To add to that...
>> >
>> > Old snapshots normally get cleaned up once a release occurs but this
>> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
>> > bits are still there. The reason is likely that the snapshot versions
>> > dont align with the end release version used, as the snapshots are
>> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>> > so the cleanup process isn't able to recognise that the snapshots have
>> > become stale artifacts following a release.
>> >
>> > We should probably also change to using 5.X.0-SNAPSHOT on master
>> > (before asking infra to nuke the snapshot repo) to prevent more cruft
>> > accumulating again with each future release.
>> >
>> > Robbie
>> >
>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>> me some work Robbie :)
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
On Wed, Jan 20, 2016 at 2:46 PM, Timothy Bish <ta...@gmail.com> wrote:
> On 01/20/2016 02:24 PM, Clebert Suconic wrote:
>> What about Apollo? there's still a snapshot towards it I think.
>
> It uses it's own version strategy to get around this and there's no
> planned future releases so I don't think we need to mess with it.
ok... I was just checking...
anyway.. I had already been looking before I got your reply: this
build will/would deploy the snapshot:
https://builds.apache.org/view/A-D/view/ActiveMQ/job/ActiveMQ-Apollo-Deploy/
And the version is at 99-trunk-SNAPSHOT, so again.. no issues.
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
On 01/20/2016 02:24 PM, Clebert Suconic wrote:
> What about Apollo? there's still a snapshot towards it I think.
It uses it's own version strategy to get around this and there's no
planned future releases so I don't think we need to mess with it.
>
> On Wed, Jan 20, 2016 at 2:17 PM, Timothy Bish <ta...@gmail.com> wrote:
>> Now that we've updated the master branches on ActiveMQ and Artemis to
>> our intended next release snapshot versions I've opened an issue with
>> Infra to clean out the snapshots repository and let the automated builds
>> repopulate:
>>
>> https://issues.apache.org/jira/browse/INFRA-11100
>>
>>
>>
>> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>>
>>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>>
>>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>>> complaints.
>>>>>>>
>>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>
>>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>>
>>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>>> released.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>>
>>>>>>>>>>> Thoughts?
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Tim Bish
>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>>
>>>>>>>>>> Robbie
>>>>>>>>> To add to that...
>>>>>>>>>
>>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>>> become stale artifacts following a release.
>>>>>>>>>
>>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>>> accumulating again with each future release.
>>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>>>
>>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>>> me some work Robbie :)
>>>>>>>>
>>>>>>>> --
>>>>>>>> Tim Bish
>>>>>>>> twitter: @tabish121
>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>> We should move all the maintained branches to the correct version
>>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>>> so master, 5.13.x etc
>>>>>>
>>>>> Yep. Looks like master is the only culprit at the moment.
>>>>>
>>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>>> objections raised here so far. I doubt too many folks will be
>>>>> depending on the old version, but updating from a given snapshot
>>>>> version to another version (release or otherwise) is generally to be
>>>>> expected if you are anyway.
>>>>>
>>>>> Robbie
>>>>>
>>>> Agreed, since there's been no objections I've gone ahead and updated
>>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>>> go.
>>>>
>>>> --
>>>> Tim Bish
>>>> twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>>>
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>
>
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
What about Apollo? there's still a snapshot towards it I think.
On Wed, Jan 20, 2016 at 2:17 PM, Timothy Bish <ta...@gmail.com> wrote:
> Now that we've updated the master branches on ActiveMQ and Artemis to
> our intended next release snapshot versions I've opened an issue with
> Infra to clean out the snapshots repository and let the automated builds
> repopulate:
>
> https://issues.apache.org/jira/browse/INFRA-11100
>
>
>
> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>
>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>
>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>> complaints.
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>
>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>> wrote:
>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>
>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>> released.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>
>>>>>>>>>> Thoughts?
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Tim Bish
>>>>>>>>>> twitter: @tabish121
>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>> To add to that...
>>>>>>>>
>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>> become stale artifacts following a release.
>>>>>>>>
>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>> accumulating again with each future release.
>>>>>>>>
>>>>>>>> Robbie
>>>>>>>>
>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>> me some work Robbie :)
>>>>>>>
>>>>>>> --
>>>>>>> Tim Bish
>>>>>>> twitter: @tabish121
>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>
>>>>>>>
>>>>> We should move all the maintained branches to the correct version
>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>> so master, 5.13.x etc
>>>>>
>>>> Yep. Looks like master is the only culprit at the moment.
>>>>
>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>> objections raised here so far. I doubt too many folks will be
>>>> depending on the old version, but updating from a given snapshot
>>>> version to another version (release or otherwise) is generally to be
>>>> expected if you are anyway.
>>>>
>>>> Robbie
>>>>
>>> Agreed, since there's been no objections I've gone ahead and updated
>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>> go.
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
>>
>>
>
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
On 01/26/2016 06:17 PM, Robbie Gemmell wrote:
> Yeah, I can only think that for build #70 the required old
> 1.1.1-SNAPSHOT bits being referenced were still in the local repo on
> that node from a previous build which let it work, but werent where
> #69 ran so it failed. Shouldnt be an issue going forward.
Nice work all, repo looks much nicer now that the ancient builds are all
gone :)
>
> On 26 January 2016 at 23:04, Clebert Suconic <cl...@gmail.com> wrote:
>> I had a mistake on a few examples.. and for some weird error 70
>> succeeded creating the 1.1.1 that you probably saw? It's fixed now,
>> and it shouldn't happen again.
>>
>> On Tue, Jan 26, 2016 at 2:40 PM, Robbie Gemmell
>> <ro...@gmail.com> wrote:
>>> I ran the Artemis job again after Clebert fixed the example poms
>>> (thanks!), so the updated 1.3.0-SNAPSHOT files for Artemis are now in
>>> place:
>>> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/71/
>>>
>>> I've updated the INFRA ticket asking for the couple of stale
>>> 1.1.1-SNAPSHOT bits (that I'm not entirely sure how successfully came
>>> to actually get in there again) to be cleared out.
>>>
>>> Robbie
>>>
>>> On 26 January 2016 at 10:15, Robbie Gemmell <ro...@gmail.com> wrote:
>>>> Infra have now blown the repo contents away. The ActiveMQ 5 deploy job
>>>> has run to publish a new 5.14.0-SNAPSHOT.
>>>>
>>>> The nightly Artemis deploy job failed because the build seems to
>>>> reference some of the older snapshot artifacts that got deleted:
>>>> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/69/
>>>>
>>>> Robbie
>>>>
>>>> On 20 January 2016 at 19:17, Timothy Bish <ta...@gmail.com> wrote:
>>>>> Now that we've updated the master branches on ActiveMQ and Artemis to
>>>>> our intended next release snapshot versions I've opened an issue with
>>>>> Infra to clean out the snapshots repository and let the automated builds
>>>>> repopulate:
>>>>>
>>>>> https://issues.apache.org/jira/browse/INFRA-11100
>>>>>
>>>>>
>>>>>
>>>>> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>>>>>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>>>>>
>>>>>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>>>>>
>>>>>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>>>>>> complaints.
>>>>>>>>>>
>>>>>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>>>>>> released.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Tim Bish
>>>>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Robbie
>>>>>>>>>>>> To add to that...
>>>>>>>>>>>>
>>>>>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>>>>>> become stale artifacts following a release.
>>>>>>>>>>>>
>>>>>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>>>>>> accumulating again with each future release.
>>>>>>>>>>>>
>>>>>>>>>>>> Robbie
>>>>>>>>>>>>
>>>>>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>>>>>> me some work Robbie :)
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Tim Bish
>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> We should move all the maintained branches to the correct version
>>>>>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>>>>>> so master, 5.13.x etc
>>>>>>>>>
>>>>>>>> Yep. Looks like master is the only culprit at the moment.
>>>>>>>>
>>>>>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>>>>>> objections raised here so far. I doubt too many folks will be
>>>>>>>> depending on the old version, but updating from a given snapshot
>>>>>>>> version to another version (release or otherwise) is generally to be
>>>>>>>> expected if you are anyway.
>>>>>>>>
>>>>>>>> Robbie
>>>>>>>>
>>>>>>> Agreed, since there's been no objections I've gone ahead and updated
>>>>>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>>>>>> go.
>>>>>>>
>>>>>>> --
>>>>>>> Tim Bish
>>>>>>> twitter: @tabish121
>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Tim Bish
>>>>> twitter: @tabish121
>>>>> blog: http://timbish.blogspot.com/
>>>>>
>>
>>
>> --
>> Clebert Suconic
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
Yeah, I can only think that for build #70 the required old
1.1.1-SNAPSHOT bits being referenced were still in the local repo on
that node from a previous build which let it work, but werent where
#69 ran so it failed. Shouldnt be an issue going forward.
On 26 January 2016 at 23:04, Clebert Suconic <cl...@gmail.com> wrote:
> I had a mistake on a few examples.. and for some weird error 70
> succeeded creating the 1.1.1 that you probably saw? It's fixed now,
> and it shouldn't happen again.
>
> On Tue, Jan 26, 2016 at 2:40 PM, Robbie Gemmell
> <ro...@gmail.com> wrote:
>> I ran the Artemis job again after Clebert fixed the example poms
>> (thanks!), so the updated 1.3.0-SNAPSHOT files for Artemis are now in
>> place:
>> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/71/
>>
>> I've updated the INFRA ticket asking for the couple of stale
>> 1.1.1-SNAPSHOT bits (that I'm not entirely sure how successfully came
>> to actually get in there again) to be cleared out.
>>
>> Robbie
>>
>> On 26 January 2016 at 10:15, Robbie Gemmell <ro...@gmail.com> wrote:
>>> Infra have now blown the repo contents away. The ActiveMQ 5 deploy job
>>> has run to publish a new 5.14.0-SNAPSHOT.
>>>
>>> The nightly Artemis deploy job failed because the build seems to
>>> reference some of the older snapshot artifacts that got deleted:
>>> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/69/
>>>
>>> Robbie
>>>
>>> On 20 January 2016 at 19:17, Timothy Bish <ta...@gmail.com> wrote:
>>>> Now that we've updated the master branches on ActiveMQ and Artemis to
>>>> our intended next release snapshot versions I've opened an issue with
>>>> Infra to clean out the snapshots repository and let the automated builds
>>>> repopulate:
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-11100
>>>>
>>>>
>>>>
>>>> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>>>>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>>>>
>>>>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>>>>
>>>>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>>>>> complaints.
>>>>>>>>>
>>>>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>>>>> released.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Tim Bish
>>>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>>>>
>>>>>>>>>>>> Robbie
>>>>>>>>>>> To add to that...
>>>>>>>>>>>
>>>>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>>>>> become stale artifacts following a release.
>>>>>>>>>>>
>>>>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>>>>> accumulating again with each future release.
>>>>>>>>>>>
>>>>>>>>>>> Robbie
>>>>>>>>>>>
>>>>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>>>>> me some work Robbie :)
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Tim Bish
>>>>>>>>>> twitter: @tabish121
>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> We should move all the maintained branches to the correct version
>>>>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>>>>> so master, 5.13.x etc
>>>>>>>>
>>>>>>> Yep. Looks like master is the only culprit at the moment.
>>>>>>>
>>>>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>>>>> objections raised here so far. I doubt too many folks will be
>>>>>>> depending on the old version, but updating from a given snapshot
>>>>>>> version to another version (release or otherwise) is generally to be
>>>>>>> expected if you are anyway.
>>>>>>>
>>>>>>> Robbie
>>>>>>>
>>>>>> Agreed, since there's been no objections I've gone ahead and updated
>>>>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>>>>> go.
>>>>>>
>>>>>> --
>>>>>> Tim Bish
>>>>>> twitter: @tabish121
>>>>>> blog: http://timbish.blogspot.com/
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Tim Bish
>>>> twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>
>
>
> --
> Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
I had a mistake on a few examples.. and for some weird error 70
succeeded creating the 1.1.1 that you probably saw? It's fixed now,
and it shouldn't happen again.
On Tue, Jan 26, 2016 at 2:40 PM, Robbie Gemmell
<ro...@gmail.com> wrote:
> I ran the Artemis job again after Clebert fixed the example poms
> (thanks!), so the updated 1.3.0-SNAPSHOT files for Artemis are now in
> place:
> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/71/
>
> I've updated the INFRA ticket asking for the couple of stale
> 1.1.1-SNAPSHOT bits (that I'm not entirely sure how successfully came
> to actually get in there again) to be cleared out.
>
> Robbie
>
> On 26 January 2016 at 10:15, Robbie Gemmell <ro...@gmail.com> wrote:
>> Infra have now blown the repo contents away. The ActiveMQ 5 deploy job
>> has run to publish a new 5.14.0-SNAPSHOT.
>>
>> The nightly Artemis deploy job failed because the build seems to
>> reference some of the older snapshot artifacts that got deleted:
>> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/69/
>>
>> Robbie
>>
>> On 20 January 2016 at 19:17, Timothy Bish <ta...@gmail.com> wrote:
>>> Now that we've updated the master branches on ActiveMQ and Artemis to
>>> our intended next release snapshot versions I've opened an issue with
>>> Infra to clean out the snapshots repository and let the automated builds
>>> repopulate:
>>>
>>> https://issues.apache.org/jira/browse/INFRA-11100
>>>
>>>
>>>
>>> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>>>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>>>
>>>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>>>
>>>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>>>> complaints.
>>>>>>>>
>>>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>>>
>>>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>>>> released.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>>>
>>>>>>>>>>>> Thoughts?
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Tim Bish
>>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>>>
>>>>>>>>>>> Robbie
>>>>>>>>>> To add to that...
>>>>>>>>>>
>>>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>>>> become stale artifacts following a release.
>>>>>>>>>>
>>>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>>>> accumulating again with each future release.
>>>>>>>>>>
>>>>>>>>>> Robbie
>>>>>>>>>>
>>>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>>>> me some work Robbie :)
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Tim Bish
>>>>>>>>> twitter: @tabish121
>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>> We should move all the maintained branches to the correct version
>>>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>>>> so master, 5.13.x etc
>>>>>>>
>>>>>> Yep. Looks like master is the only culprit at the moment.
>>>>>>
>>>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>>>> objections raised here so far. I doubt too many folks will be
>>>>>> depending on the old version, but updating from a given snapshot
>>>>>> version to another version (release or otherwise) is generally to be
>>>>>> expected if you are anyway.
>>>>>>
>>>>>> Robbie
>>>>>>
>>>>> Agreed, since there's been no objections I've gone ahead and updated
>>>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>>>> go.
>>>>>
>>>>> --
>>>>> Tim Bish
>>>>> twitter: @tabish121
>>>>> blog: http://timbish.blogspot.com/
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
I ran the Artemis job again after Clebert fixed the example poms
(thanks!), so the updated 1.3.0-SNAPSHOT files for Artemis are now in
place:
https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/71/
I've updated the INFRA ticket asking for the couple of stale
1.1.1-SNAPSHOT bits (that I'm not entirely sure how successfully came
to actually get in there again) to be cleared out.
Robbie
On 26 January 2016 at 10:15, Robbie Gemmell <ro...@gmail.com> wrote:
> Infra have now blown the repo contents away. The ActiveMQ 5 deploy job
> has run to publish a new 5.14.0-SNAPSHOT.
>
> The nightly Artemis deploy job failed because the build seems to
> reference some of the older snapshot artifacts that got deleted:
> https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/69/
>
> Robbie
>
> On 20 January 2016 at 19:17, Timothy Bish <ta...@gmail.com> wrote:
>> Now that we've updated the master branches on ActiveMQ and Artemis to
>> our intended next release snapshot versions I've opened an issue with
>> Infra to clean out the snapshots repository and let the automated builds
>> repopulate:
>>
>> https://issues.apache.org/jira/browse/INFRA-11100
>>
>>
>>
>> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>>
>>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>>
>>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>>> complaints.
>>>>>>>
>>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>
>>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>>
>>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>>> released.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>>
>>>>>>>>>>> Thoughts?
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Tim Bish
>>>>>>>>>>> twitter: @tabish121
>>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>>
>>>>>>>>>> Robbie
>>>>>>>>> To add to that...
>>>>>>>>>
>>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>>> become stale artifacts following a release.
>>>>>>>>>
>>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>>> accumulating again with each future release.
>>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>>>
>>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>>> me some work Robbie :)
>>>>>>>>
>>>>>>>> --
>>>>>>>> Tim Bish
>>>>>>>> twitter: @tabish121
>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>> We should move all the maintained branches to the correct version
>>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>>> so master, 5.13.x etc
>>>>>>
>>>>> Yep. Looks like master is the only culprit at the moment.
>>>>>
>>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>>> objections raised here so far. I doubt too many folks will be
>>>>> depending on the old version, but updating from a given snapshot
>>>>> version to another version (release or otherwise) is generally to be
>>>>> expected if you are anyway.
>>>>>
>>>>> Robbie
>>>>>
>>>> Agreed, since there's been no objections I've gone ahead and updated
>>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>>> go.
>>>>
>>>> --
>>>> Tim Bish
>>>> twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>>>
>>>
>>
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
Infra have now blown the repo contents away. The ActiveMQ 5 deploy job
has run to publish a new 5.14.0-SNAPSHOT.
The nightly Artemis deploy job failed because the build seems to
reference some of the older snapshot artifacts that got deleted:
https://builds.apache.org/view/A-D/view/ActiveMQ/job/Artemis-deploy/69/
Robbie
On 20 January 2016 at 19:17, Timothy Bish <ta...@gmail.com> wrote:
> Now that we've updated the master branches on ActiveMQ and Artemis to
> our intended next release snapshot versions I've opened an issue with
> Infra to clean out the snapshots repository and let the automated builds
> repopulate:
>
> https://issues.apache.org/jira/browse/INFRA-11100
>
>
>
> On 01/20/2016 12:48 PM, Clebert Suconic wrote:
>> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>>
>> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>>
>>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>>> complaints.
>>>>>>
>>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>
>>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>>> wrote:
>>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>>
>>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>>> released.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>>
>>>>>>>>>> Thoughts?
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Tim Bish
>>>>>>>>>> twitter: @tabish121
>>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>>
>>>>>>>>> Robbie
>>>>>>>> To add to that...
>>>>>>>>
>>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>>> become stale artifacts following a release.
>>>>>>>>
>>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>>> accumulating again with each future release.
>>>>>>>>
>>>>>>>> Robbie
>>>>>>>>
>>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>>> me some work Robbie :)
>>>>>>>
>>>>>>> --
>>>>>>> Tim Bish
>>>>>>> twitter: @tabish121
>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>
>>>>>>>
>>>>> We should move all the maintained branches to the correct version
>>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>>> so master, 5.13.x etc
>>>>>
>>>> Yep. Looks like master is the only culprit at the moment.
>>>>
>>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>>> objections raised here so far. I doubt too many folks will be
>>>> depending on the old version, but updating from a given snapshot
>>>> version to another version (release or otherwise) is generally to be
>>>> expected if you are anyway.
>>>>
>>>> Robbie
>>>>
>>> Agreed, since there's been no objections I've gone ahead and updated
>>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>>> go.
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
>>
>>
>
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
Now that we've updated the master branches on ActiveMQ and Artemis to
our intended next release snapshot versions I've opened an issue with
Infra to clean out the snapshots repository and let the automated builds
repopulate:
https://issues.apache.org/jira/browse/INFRA-11100
On 01/20/2016 12:48 PM, Clebert Suconic wrote:
> artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
>
> On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>>
>>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>>> complaints.
>>>>>
>>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>>
>>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>>> wrote:
>>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>>
>>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>>> released.
>>>>>>>>>
>>>>>>>>>
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Tim Bish
>>>>>>>>> twitter: @tabish121
>>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>>
>>>>>>>> Robbie
>>>>>>> To add to that...
>>>>>>>
>>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>>> dont align with the end release version used, as the snapshots are
>>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>>> become stale artifacts following a release.
>>>>>>>
>>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>>> accumulating again with each future release.
>>>>>>>
>>>>>>> Robbie
>>>>>>>
>>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>>> me some work Robbie :)
>>>>>>
>>>>>> --
>>>>>> Tim Bish
>>>>>> twitter: @tabish121
>>>>>> blog: http://timbish.blogspot.com/
>>>>>>
>>>>>>
>>>> We should move all the maintained branches to the correct version
>>>> numbering anyway so future releases purge their snapshots from the repo,
>>>> so master, 5.13.x etc
>>>>
>>> Yep. Looks like master is the only culprit at the moment.
>>>
>>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>>> objections raised here so far. I doubt too many folks will be
>>> depending on the old version, but updating from a given snapshot
>>> version to another version (release or otherwise) is generally to be
>>> expected if you are anyway.
>>>
>>> Robbie
>>>
>> Agreed, since there's been no objections I've gone ahead and updated
>> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
>> go.
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>
>
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Clebert Suconic <cl...@gmail.com>.
artemis was bumped also: https://github.com/apache/activemq-artemis/pull/331
On Wed, Jan 20, 2016 at 12:43 PM, Timothy Bish <ta...@gmail.com> wrote:
> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>>
>>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>>> complaints.
>>>>
>>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>>
>>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>>> wrote:
>>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>>
>>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>>> released.
>>>>>>>>
>>>>>>>>
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>>
>>>>>>>> --
>>>>>>>> Tim Bish
>>>>>>>> twitter: @tabish121
>>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>>
>>>>>>> Robbie
>>>>>> To add to that...
>>>>>>
>>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>>> dont align with the end release version used, as the snapshots are
>>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>>> become stale artifacts following a release.
>>>>>>
>>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>>> accumulating again with each future release.
>>>>>>
>>>>>> Robbie
>>>>>>
>>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>>> me some work Robbie :)
>>>>>
>>>>> --
>>>>> Tim Bish
>>>>> twitter: @tabish121
>>>>> blog: http://timbish.blogspot.com/
>>>>>
>>>>>
>>> We should move all the maintained branches to the correct version
>>> numbering anyway so future releases purge their snapshots from the repo,
>>> so master, 5.13.x etc
>>>
>> Yep. Looks like master is the only culprit at the moment.
>>
>> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
>> objections raised here so far. I doubt too many folks will be
>> depending on the old version, but updating from a given snapshot
>> version to another version (release or otherwise) is generally to be
>> expected if you are anyway.
>>
>> Robbie
>>
> Agreed, since there's been no objections I've gone ahead and updated
> ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
> go.
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
--
Clebert Suconic
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
> On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
>> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>>
>>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>>> complaints.
>>>
>>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>>
>>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>>> wrote:
>>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>>
>>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>>> released.
>>>>>>>
>>>>>>>
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>>
>>>>>>> Thoughts?
>>>>>>>
>>>>>>> --
>>>>>>> Tim Bish
>>>>>>> twitter: @tabish121
>>>>>>> blog: http://timbish.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>>
>>>>>> Robbie
>>>>> To add to that...
>>>>>
>>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>>> bits are still there. The reason is likely that the snapshot versions
>>>>> dont align with the end release version used, as the snapshots are
>>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>>> become stale artifacts following a release.
>>>>>
>>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>>> accumulating again with each future release.
>>>>>
>>>>> Robbie
>>>>>
>>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>>> me some work Robbie :)
>>>>
>>>> --
>>>> Tim Bish
>>>> twitter: @tabish121
>>>> blog: http://timbish.blogspot.com/
>>>>
>>>>
>> We should move all the maintained branches to the correct version
>> numbering anyway so future releases purge their snapshots from the repo,
>> so master, 5.13.x etc
>>
> Yep. Looks like master is the only culprit at the moment.
>
> Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
> objections raised here so far. I doubt too many folks will be
> depending on the old version, but updating from a given snapshot
> version to another version (release or otherwise) is generally to be
> expected if you are anyway.
>
> Robbie
>
Agreed, since there's been no objections I've gone ahead and updated
ActiveMQ master to 5.14.0-SNAPSHOT, rest of the 5.x branches are good to
go.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
On 20 January 2016 at 15:16, Timothy Bish <ta...@gmail.com> wrote:
> On 01/20/2016 07:26 AM, Christopher Shannon wrote:
>> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
>> X.X-SNAPSHOT for development versions so this makes sense to me.
>>
>> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
>> complaints.
>>
>> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>>
>>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>>> wrote:
>>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>>
>>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>>> released.
>>>>>>
>>>>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>>> We can request that infra wipe out the snapshots area and let the
>>>>>> jenkins runs repopulate with only the current builds for active project
>>>>>> work. Alternatively we can go through every folder and audit them but
>>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> --
>>>>>> Tim Bish
>>>>>> twitter: @tabish121
>>>>>> blog: http://timbish.blogspot.com/
>>>>>>
>>>>>>
>>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>>> and I'm not sure infra would be particularly happy at being asked that
>>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>>
>>>>> Robbie
>>>> To add to that...
>>>>
>>>> Old snapshots normally get cleaned up once a release occurs but this
>>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>>> bits are still there. The reason is likely that the snapshot versions
>>>> dont align with the end release version used, as the snapshots are
>>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>>> so the cleanup process isn't able to recognise that the snapshots have
>>>> become stale artifacts following a release.
>>>>
>>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>>> accumulating again with each future release.
>>>>
>>>> Robbie
>>>>
>>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>>> me some work Robbie :)
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
>>>
> We should move all the maintained branches to the correct version
> numbering anyway so future releases purge their snapshots from the repo,
> so master, 5.13.x etc
>
Yep. Looks like master is the only culprit at the moment.
Shall we just go ahead and update it to 5.14.0-SNAPSHOT then? No
objections raised here so far. I doubt too many folks will be
depending on the old version, but updating from a given snapshot
version to another version (release or otherwise) is generally to be
expected if you are anyway.
Robbie
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
On 01/20/2016 07:26 AM, Christopher Shannon wrote:
> +1 for the version change...I've always used X.X.0-SNAPSHOT and not
> X.X-SNAPSHOT for development versions so this makes sense to me.
>
> I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
> complaints.
>
> On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
>
>> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
>>> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
>> wrote:
>>>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>>>
>>>>> Some examples of old snapshots or snapshot to things that were never
>>>>> released.
>>>>>
>>>>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>>> We can request that infra wipe out the snapshots area and let the
>>>>> jenkins runs repopulate with only the current builds for active project
>>>>> work. Alternatively we can go through every folder and audit them but
>>>>> given they are snapshots it's simpler just to blow them all away.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> --
>>>>> Tim Bish
>>>>> twitter: @tabish121
>>>>> blog: http://timbish.blogspot.com/
>>>>>
>>>>>
>>>> Cleaning things up would definitely be good. Given the sizable amount
>>>> of cruft I dont think it makes sense to try pruning them individually,
>>>> and I'm not sure infra would be particularly happy at being asked that
>>>> either hehe, so the full wipe seems like the way to go to me.
>>>>
>>>> Robbie
>>> To add to that...
>>>
>>> Old snapshots normally get cleaned up once a release occurs but this
>>> isn't happening for the ActiveMQ 5.X bits, which is why all those old
>>> bits are still there. The reason is likely that the snapshot versions
>>> dont align with the end release version used, as the snapshots are
>>> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
>>> so the cleanup process isn't able to recognise that the snapshots have
>>> become stale artifacts following a release.
>>>
>>> We should probably also change to using 5.X.0-SNAPSHOT on master
>>> (before asking infra to nuke the snapshot repo) to prevent more cruft
>>> accumulating again with each future release.
>>>
>>> Robbie
>>>
>> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
>> me some work Robbie :)
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>
We should move all the maintained branches to the correct version
numbering anyway so future releases purge their snapshots from the repo,
so master, 5.13.x etc
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Christopher Shannon <ch...@gmail.com>.
+1 for the version change...I've always used X.X.0-SNAPSHOT and not
X.X-SNAPSHOT for development versions so this makes sense to me.
I can change the current 5.14-SNAPSHOT to 5.14.0-SNAPSHOT if no one has any
complaints.
On Tue, Jan 19, 2016 at 4:39 PM, Timothy Bish <ta...@gmail.com> wrote:
> On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
> > On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com>
> wrote:
> >> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
> >>> We seem to have a bit of a mess in our snapshots area with lots of old
> >>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
> >>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
> >>>
> >>> Some examples of old snapshots or snapshot to things that were never
> >>> released.
> >>>
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
> >>>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
> >>>
> >>> We can request that infra wipe out the snapshots area and let the
> >>> jenkins runs repopulate with only the current builds for active project
> >>> work. Alternatively we can go through every folder and audit them but
> >>> given they are snapshots it's simpler just to blow them all away.
> >>>
> >>> Thoughts?
> >>>
> >>> --
> >>> Tim Bish
> >>> twitter: @tabish121
> >>> blog: http://timbish.blogspot.com/
> >>>
> >>>
> >> Cleaning things up would definitely be good. Given the sizable amount
> >> of cruft I dont think it makes sense to try pruning them individually,
> >> and I'm not sure infra would be particularly happy at being asked that
> >> either hehe, so the full wipe seems like the way to go to me.
> >>
> >> Robbie
> >
> > To add to that...
> >
> > Old snapshots normally get cleaned up once a release occurs but this
> > isn't happening for the ActiveMQ 5.X bits, which is why all those old
> > bits are still there. The reason is likely that the snapshot versions
> > dont align with the end release version used, as the snapshots are
> > using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
> > so the cleanup process isn't able to recognise that the snapshots have
> > become stale artifacts following a release.
> >
> > We should probably also change to using 5.X.0-SNAPSHOT on master
> > (before asking infra to nuke the snapshot repo) to prevent more cruft
> > accumulating again with each future release.
> >
> > Robbie
> >
> Exactly. Hadn't gotten around to typing that up yet, thanks for saving
> me some work Robbie :)
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Timothy Bish <ta...@gmail.com>.
On 01/19/2016 04:34 PM, Robbie Gemmell wrote:
> On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com> wrote:
>> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>>> We seem to have a bit of a mess in our snapshots area with lots of old
>>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>>
>>> Some examples of old snapshots or snapshot to things that were never
>>> released.
>>>
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>>
>>> We can request that infra wipe out the snapshots area and let the
>>> jenkins runs repopulate with only the current builds for active project
>>> work. Alternatively we can go through every folder and audit them but
>>> given they are snapshots it's simpler just to blow them all away.
>>>
>>> Thoughts?
>>>
>>> --
>>> Tim Bish
>>> twitter: @tabish121
>>> blog: http://timbish.blogspot.com/
>>>
>>>
>> Cleaning things up would definitely be good. Given the sizable amount
>> of cruft I dont think it makes sense to try pruning them individually,
>> and I'm not sure infra would be particularly happy at being asked that
>> either hehe, so the full wipe seems like the way to go to me.
>>
>> Robbie
>
> To add to that...
>
> Old snapshots normally get cleaned up once a release occurs but this
> isn't happening for the ActiveMQ 5.X bits, which is why all those old
> bits are still there. The reason is likely that the snapshot versions
> dont align with the end release version used, as the snapshots are
> using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
> so the cleanup process isn't able to recognise that the snapshots have
> become stale artifacts following a release.
>
> We should probably also change to using 5.X.0-SNAPSHOT on master
> (before asking infra to nuke the snapshot repo) to prevent more cruft
> accumulating again with each future release.
>
> Robbie
>
Exactly. Hadn't gotten around to typing that up yet, thanks for saving
me some work Robbie :)
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
On 18 January 2016 at 18:46, Robbie Gemmell <ro...@gmail.com> wrote:
> On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
>> We seem to have a bit of a mess in our snapshots area with lots of old
>> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
>> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>>
>> Some examples of old snapshots or snapshot to things that were never
>> released.
>>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
>> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>>
>> We can request that infra wipe out the snapshots area and let the
>> jenkins runs repopulate with only the current builds for active project
>> work. Alternatively we can go through every folder and audit them but
>> given they are snapshots it's simpler just to blow them all away.
>>
>> Thoughts?
>>
>> --
>> Tim Bish
>> twitter: @tabish121
>> blog: http://timbish.blogspot.com/
>>
>>
>
> Cleaning things up would definitely be good. Given the sizable amount
> of cruft I dont think it makes sense to try pruning them individually,
> and I'm not sure infra would be particularly happy at being asked that
> either hehe, so the full wipe seems like the way to go to me.
>
> Robbie
To add to that...
Old snapshots normally get cleaned up once a release occurs but this
isn't happening for the ActiveMQ 5.X bits, which is why all those old
bits are still there. The reason is likely that the snapshot versions
dont align with the end release version used, as the snapshots are
using 5.X-SNAPSHOT but the released bits then actually use 5.X.0, and
so the cleanup process isn't able to recognise that the snapshots have
become stale artifacts following a release.
We should probably also change to using 5.X.0-SNAPSHOT on master
(before asking infra to nuke the snapshot repo) to prevent more cruft
accumulating again with each future release.
Robbie
Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Posted by Robbie Gemmell <ro...@gmail.com>.
On 18 January 2016 at 15:53, Timothy Bish <ta...@gmail.com> wrote:
> We seem to have a bit of a mess in our snapshots area with lots of old
> snapshots for ancient releases like 5.3, 5.4, etc along with snapshots
> for an ActiveMQ 6.0.0 release that has caused some confusion recently.
>
> Some examples of old snapshots or snapshot to things that were never
> released.
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-aerogear-integration/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-all/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-book/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-bootstrap/
> https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-core-client/
>
> We can request that infra wipe out the snapshots area and let the
> jenkins runs repopulate with only the current builds for active project
> work. Alternatively we can go through every folder and audit them but
> given they are snapshots it's simpler just to blow them all away.
>
> Thoughts?
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>
Cleaning things up would definitely be good. Given the sizable amount
of cruft I dont think it makes sense to try pruning them individually,
and I'm not sure infra would be particularly happy at being asked that
either hehe, so the full wipe seems like the way to go to me.
Robbie