Colin Putney <[email protected]> napisał: >On Tue, Jun 2, 2015 at 9:15 AM, Colin Putney <[email protected]> >wrote: > >> Hi all, >> >> I'm running a small cluster with several custom-built services, and >I'd >> like to include git commit hashes in my logs so that I can easily >find the >> source code that's producing them. I thought this would be >> straight-forward, but it's turning out to be surprisingly difficult. >> >> Running `git describe` >> > >Ugh, premature send. Sorry. > >In principle, including the git hash in the output of a build should be >deterministic: for any given working copy, there is one and only one >commit >hash. In practice, though, running git describe without introducing >impurity seems to be impossible. Anybody figured out how to do this?
You can pass leaveDotGit = true into fetchgit, or pass the commit into the build script as a separate variable. >Colin > > >------------------------------------------------------------------------ > >_______________________________________________ >nix-dev mailing list >[email protected] >http://lists.science.uu.nl/mailman/listinfo/nix-dev -- Wysłane za pomocą K-9 Mail. _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
