write and deploy a buildbot step that builds and tests the Mac OS X package #2360

New Issue

tahoe-lafs · 2015-01-13T17:22:57Z

daira commented

2015-01-13 17:22:57 +00:00

Dependent on #2303, #2304 and #182.

tahoe-lafs added the

labels 2015-01-13 17:22:57 +00:00

tahoe-lafs added this to the soon (release n/a) milestone 2015-01-13 17:22:57 +00:00

warner commented

2015-03-20 19:37:08 +00:00

The buildbot step is deployed. It runs:

make build-osx-pkg (which also tests it)
python misc/build_helpers/test-osx-pkg.py (which is redundant, but clear)
make upload-osx-pkg

The upload step uses a flappclient to copy the .pkg file to tahoe-lafs.org .

So I think we can close this. I've opened #2393 to address one of the remaining usability issues (the .pkg files always get the same name).

The buildbot step is deployed. It runs: * `make build-osx-pkg` (which also tests it) * `python misc/build_helpers/test-osx-pkg.py` (which is redundant, but clear) * `make upload-osx-pkg` The upload step uses a flappclient to copy the .pkg file to tahoe-lafs.org . So I think we can close this. I've opened #2393 to address one of the remaining usability issues (the .pkg files always get the same name).