Geek Answers Handbook

Attaching Binary Code to a Git Tag

I am developing mobile applications (iPhone, Android and Blackberry) and have recently converted from SVN to Git.

After releasing it in SVN, I mark the corresponding branch / revision to make sure that its state is saved, and then I add the directory to this tag and put the debugging files in the released binary file as well (for iPhone) for this is an exact assembly (for later symbolic description of any alarms). Files do not need versions, but this is a convenient place to store historical artifacts together with code to ensure their backup (SVN has a backup policy, while assemblies on my CI server do not work).

I am trying to find the best equivalent in git. Probably the closest thing would be to create a new branch, add binaries, tag it, and delete the branch. However, I am wondering if there are better ways to do this?

Ideally, I would like to create a tag, and then attach the binaries as untapped files to the tag. Thus, they do not actually appear in the source tree, but they are located in the repository associated with the tag, for searches as needed by anyone who has access to the repository. Is there anything equivalent to this in Git?

+5
source share
3 answers

VCS (, ), , :

  • VCS (, , diff,...)
  • DVCS ( VCS) , , .

artefact (, Nexus), checksum (SHA1, MD5) , , .

, ( VCS) .

Useless answer, git notes, blob git ( )

, git blob, () . - git -:

$ cc *.c
$ blob=$(git hash-object -w a.out)
$ git notes --ref=built add -C "$blob" HEAD

- , - , .

git-annex, git ( , , , ).

git-annex git, git.
, , , git, , - , .

+6

manpage git notes , . , ?

+2

@VonC VCS .

, git, git , , subodules.

. , , .

git , ( , ) .

git . . git.

0

More articles:


All Articles