[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [git] regarding qualifiers...
|
Paul,
Thanks for the reference! A little experimenting and I found a that "git log -1 --format=%ai" will basically get me what I need (except for OS specific reformatting).
We are currently building everything based on the latest rev. That may need to change later, but this gives me what I need for now.
Thanks much.
-Eric
On 24/01/2012 1:46 PM, Paul Webster wrote:
On Tue, Jan 24, 2012 at 1:34 PM, Eric Gwin<eric.gwin@xxxxxxxxxx> wrote:
We opted to set the qualifier to .v<builddate>-r<svn revision>, so that we'd
always be able to tie the build to the codebase. After the move we won't be
able to. I could generate a tag for every build but I'd rather not deal with
the overhead, I could ignore the issue (I'm certain it'll bite us eventually
though), or I could try to stamp based on the date/time of last check-in.
I think we are close to your option 3: We update the map qualifiers
based on the v<UTC timestamp> of the last commit to touch that bundle,
and tag the commit with its matching qualifier [1]. We do it in a
special auto-tagging step at the beginning of the build that updates
all of the releng map files [2]. We also tag the build input with
the build qualifier, I20120123-2200 for example.
It works fine with our current map based build system, but has the
advantage that the qualifier is determined by the commits, which means
in theory for the same build input you'll generate the same qualifiers
for the contained bundles.
Later,
PW
[1] http://git.eclipse.org/c/e4/org.eclipse.e4.releng.git/tree/org.eclipse.e4.builder/scripts/git-map.sh
[2] http://git.eclipse.org/c/e4/org.eclipse.e4.releng.git/tree/org.eclipse.e4.builder/scripts/git-release.sh
