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 Sat, 28 Dec 2013 00:31:50 GMT


Christopher Tubbs commented on ACCUMULO-2064:

[~mdrob] wrote:
{quote}I think this got lost in the svn -> git translation.{quote}

No, it was intentionally omitted before that (ACCUMULO-1236). Some of the reasoning for removing
it is not applicable to git as much (speed of the build, due to svn checks, or multiple revisions
representing the same version). However, there's still a concern, I think, about inconsistency/non-reproducibility
with the source release tarballs.

A good CI server will track this for you anyway in the build metadata.

> 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