[Buildbot-commits] [Buildbot] #971: Build a windows installer
Buildbot
buildbot-devel at lists.sourceforge.net
Fri Oct 29 09:37:58 UTC 2010
#971: Build a windows installer
------------------------+---------------------------------------------------
Reporter: dustin | Owner: fatman
Type: enhancement | Status: accepted
Priority: major | Milestone: 0.8.3
Version: 0.8.1 | Keywords: windows
------------------------+---------------------------------------------------
Comment(by fatman2):
(Dustin, there seems to be a block on my "fatman" account. I can't log in.
Can you help?)
Read-only issue sorted! I had revoked write-access from the web server
user to the "fossils" directory. *facepalm*
Yeah, I'm wondering about including a "download dependencies" component in
the NSIS scripts as opposed to bundling the binary packages.
Pro: less bandwidth required to clone the repo.
Con: requires a third-party NSIS plugin at compile time.
Con: depending on the plugin, /might/ reduce our version control ability.
Thoughts?
As to why I'm using a Fossil repo rather than a clone of the buildbot
repo, there are several reasons.
* It seemed to me that this could be set up as a separate project. This
way there is no danger of me cluttering the buildbot repos. Currently,
buildbot has the same dependency status as Python.
* I'm in larval mode with Fossil at the moment. This means Fossil gets
applied to everything in my life. It even makes me breakfast in the
morning. [1]
* It was really easy to set up Fossil with my Apache. (But see previous
reason.)
* I don't really know buildbot's repo structure.
* Probably other reasons I haven't thought about.
[1] the previous sentence is a lie
--
Ticket URL: <http://buildbot.net/trac/ticket/971#comment:10>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
More information about the Commits
mailing list