activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <clebert.suco...@gmail.com>
Subject Re: [DISCUSS] Purge ActiveMQ Snapshots Repo to get rid of old cruft
Date Tue, 26 Jan 2016 23:04:49 GMT
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
<robbie.gemmell@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 <robbie.gemmell@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 <tabish121@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 <tabish121@gmail.com>
wrote:
>>>>> On 01/20/2016 11:43 AM, Robbie Gemmell wrote:
>>>>>> On 20 January 2016 at 15:16, Timothy Bish <tabish121@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 <tabish121@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 <tabish121@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

Mime
View raw message