[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [buckminster-dev] Buckminster code-base has moved to Git
- From: Ian Bull <irbull@xxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2011 14:15:00 -0700
- Delivered-to: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eclipsesource.com; s=eclipsesource; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=u3yHGeOz1Pat8zTsO371TxDCuBeWF/BGc5Lp3QMlLJA=; b=EPS4ZUKAB3GoW3crWV52hevBVjNWvCo0TC4II/EdgMSxN2Z1POEa6Q78IZMGKyzfHc aCp7jdbFcDMiVnR0hVnUoS3SRved4fcFC4EAOMe4dszdthAQkC7MMybw4YGVhFp8RZy9 WTwnW+6+lwYM5jrzCNcGwnpLHfwRCRTlM48l8=
Buckminster has a qualifier generator that finds the latest commit that affects a given subtree (in this case a project). We use the timestamp of such commits directly for plug-in qualifiers. For features, we calculate the last timestamp for all included features, plug-ins, and the feature project itself and use that. There are some corner cases when this approach isn't fail proof but the way we use it, it works perfectly. Our qualifiers will remain the same as long as our code is unchanged.
Btw, are you maintaining stable qualifiers? That is, if a bundle doesn't
change from build to build are you ensuring that the qualifiers remain
the same? I'm trying to get a sense of how people are doing this with git.
And this works with Git?
I wonder if this work could be reused in Eclipse Releng Tool .
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource