<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitolite on System Overlord</title><link>https://systemoverlord.com/tags/gitolite.html</link><description>Recent content in Gitolite on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Sat, 16 Jul 2011 13:33:05 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/gitolite/index.xml" rel="self" type="application/rss+xml"/><item><title>Automatically Creating Archives from Git Tags</title><link>https://systemoverlord.com/2011/07/16/automatically-creating-archives-from-git-tags/</link><pubDate>Sat, 16 Jul 2011 13:33:05 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/07/16/automatically-creating-archives-from-git-tags/</guid><description>&lt;p&gt;At work, we've been moving all of our development processes to git. As part of that, I've encouraged that alphas, betas, and releases be tagged in git -- it's important to know which versions are in use where. Additionally, my director wanted archives (zips/tars) of each of these versions to make it easier to install the releases, particularly for the members of our department who are not git-friendly. I realized that with git hooks and our use of gitolite, we could produce automated archives when tags with the words alpha/beta/release are pushed to the gitolite server. The script below is placed in the $GL_PACKAGE_HOOKS/common directory. It uses the name of the repository to decide if it should be archived (matches $ALLOW_ARCHIVE) and where the archive should be put (within $ARCHIVE_DIR).
&lt;/p&gt;</description></item></channel></rss>