Proposed fix for rebuilding windows releases

[Geert Janssens]

The problem: when a release build for windows fails on the build server, the 
tag has to be removed, one day has to pass, another tag created and finally 
two days later, a new build appears. This is, of course, unless a developer 
with access to the build server manually resets the build.

The proposed solution: the attached patch changes the tag build script to deal 
with this. In addition to checking for new tags, the script also checks the 
tags' revisions for changes. So if a Windows build fails the release manager 
can simply untag, apply the necessary fixes and retag. The next time it's run, 
the script will detect a change in the revision for that tag, and restart the 
build. This will be a complete rebuild by the way, all traces of the previous 
(failed) build will be removed. So the next morning a new build can be 
available.

If you like it, you or I can commit this. I didn't want to do this directly 
because of this:

!! WARNING WARNING !! before installing the new script on the build server, be 
sure to remove the existing tags file !!
Its format changes with this patch. Keeping the old tags file around will 
start a rebuild of ALL tags. Simply removing the tags file will prevent this.

I don't know if the script gets installed automatically when I commit the 
changes to svn, so I'll wait for feedback of the ones in charge of the build 
server.

Geert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build_tags.sh.patch
Type: text/x-patch
Size: 1277 bytes
Desc: not available
URL: <http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20100501/77efaa83/attachment.bin>