Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] retention policy for builds

I have a simple script that generates them based on an index. The find
expression specifies which sites to include, e.g. the 10 most recent
3.5.x releases:

# cat releases/3.5/composite.index
DIRS=$(find ../../archive/3.5.*/v*/ -maxdepth 0 | sort -r | head -n 10)
NAME="Mylyn 3.5 for Eclipse 3.5, 3.6 and 3.7"

The script that generates the compositeContent.xml and
compositeArtifacts.xml is here:


On Wed, Jun 15, 2011 at 3:15 PM, Matthias Sohn
<matthias.sohn@xxxxxxxxxxxxxx> wrote:
> 2011/6/14 Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
>> What happens when 1.0.1 is released, will the updates-1.0 site still
>> have the 1.0.0 release?
>> For Mylyn we use composites for that purpose that aggregate releases
>> from an archive that retains all released versions forever (older
>> versions move to eventually). The maintenance site
>> for the each stream serves all released versions of a stream. That
>> allows integrator to use strict version constraints while still
>> providing the convenience of a site that serves the latest release.
>> The other nice property of composites sites is that you can move
>> things to the archive without affecting integrators.
> This is a good idea, I started using a composite repository for staging and
> it works well. So I can try to set this up.
> How do you maintain the composite definition files ? Any pointers how
> this is done in Mylyn ?
> --
> Matthias

Steffen Pingel
Senior Developer,

Back to the top