On Thu, Jun 30, 2011 at 10:57 AM, Eric Steele <ems174@...> wrote:
> Wyn's given me a private Jenkins instance that I intend to use for automating a good chunk of the release process. The Foundation has picked up a MSDN license so we'll be able to get Windows VMs running as well.
> I'd like to start some discussion about automating the building of installers. Since I know very little about how you go about generating those, I'll have to defer completely to you on this. What does the process look like? How much can be automated? What needs to be done by hand?
As far as the Installer for Windows goes, it's pretty automated, once
the environment has been properly setup. That basically consists of
- Windows Platform SDK (a specific version is needed)
- enfold.build (don't recall if it's up on PyPI)
- wxPython (a specific version is needed)
Then, once a new release needs to be made it's usually a matter of
fetching the latest versions.cfg and updating the plone.cfg file that
the builder uses to contain the correct version number. The only
problem that usually happens is upgrades to zc.buildout or distribute
causing buildout to exit and start over, which the build script
doesn't cope very well with. The solution to those is to pin the newer