accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2064) Include Git SHA1 in artifacts
Date Tue, 31 Dec 2013 00:02:54 GMT


Christopher Tubbs commented on ACCUMULO-2064:

[~mdrob] wrote:
{quote}I'm not sure I understand your concern about not being able to reproduce source releases.{quote}

Two things. First (and, least relevant) is that the SHA1 may not match, if somebody has mirrored
the repository without using git clone (eg. export, then import), and second (still not that
important), building from a source release tarball (the official release) will not match the
released binary from our build.

I'm inclined to agree with you that the benefits outweigh these concerns.

> Include Git SHA1 in artifacts
> -----------------------------
>                 Key: ACCUMULO-2064
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: build
>            Reporter: Josh Elser
>            Assignee: Mike Drob
>            Priority: Minor
>             Fix For: 1.4.5, 1.5.1, 1.6.0
> After building a SNAPSHOT version of Accumulo, the Git commit ID it was built from is
lost in the wind the next time you update you copy of the repo.
> It would be nice to include the SHA1 in the the MANIFEST.MF. I've done this before, and
I remember it to be rather easy in the end, but I don't remember how off the top of my head.
> This would be very useful when running Accumulo's distributed tests during at the end
of a release cycle to rule out the possibility of running into a bug that was already fixed.

This message was sent by Atlassian JIRA

View raw message