Toolchain tracking
-
I’d like to do a better job of recording what environmnent and git commit id produce a trunk/ commit.
What’s the best way to record the contents of the following file created in /tmp/ in a trunk/ commit?# # get build info # rm -rf /tmp/.git-commit-id tree=
git symbolic-ref --short HEAD
COMPILER=php -v | head -1
VERSION=git log $tree --decorate | head -1
printf "%s\n%s\n" $COMPILER $VERSION > /tmp/.git-commit-idI can’t put this file into a .zip intended for installation via
git archive --output=$NAME.zip $TREE $PATH --add-file=/tmp/.git-commit-id
I’m thinking the best way to do this is a substitution sentinal in the README . An unused header (for retrieval via grep) field?
- The topic ‘Toolchain tracking’ is closed to new replies.