We have two options here:

1. Either the current autobuild server uses deenosaurier as a service to have a mac-build built, then downloads it from there and uploads it to openclonk.org via FTP, updates the version in the DB etc.
2. Or, deenosaurier is notified in the same commit hook as the win/linux autobuild server from git and does everything itself, no remote control: build mac-build, upload it to FTP, update version in the DB

Option 2 might be easier to code, but as yourself I lean towards option 1 since I think it is easier to manage plus the code from there can be reused. Also, we have only one autobuild server then, so only one system that has write access to FTP and DB. The other argument that speaks for option 1 is that on the win/linux autobuild server (you know, we really need a name for it ;-)), the OC* folders have already been created, so no need to do it twice.

However, for option 1 you need to stick your head together with Clonk-Karl or perhaps Isilkor if he has been wise enough to appoint a co-admin on the autobuild-stuff because he seems to be currently absent from the forum. Otherwise, just email him. There is a repository for the autobuild scripts, you will need access to that. (Perhaps just for reference, you should upload the osxbuildings.js there as well so that we have it somewhere in a repository.)
From that repository, you can also see how the other build targets are achieved, so building the final code for the osx-autobuilds might be as easy as copy&pasting from the linux build targets.

Clonk-Karl: Would it be sensible by the way to move the autobuild-scripts to a repository on git.openclonk.org? It would be good to have all reachable in one place, IIRC there is no sensitive information in the repository itself, is there?

>Stupid idea? I have no clue about network security? Mac builds are stupid anyways? Discuss.

Also, start being proud on your achievements! I find this whole WOL stuff ingenious!

Just a few abbreviations I want to introduce before this post: deeno = deenosaurier, Mortimer's build mac service; autobuild = Isilkor's autobuild scripts on nosebud; nightly = CK's development snapshot scripts

Based on CK's and Isilkor's reply I would suggest the following structure to enable even mac autobuilds and make the deenosaurier fit into the current build structure. The basic idea is to make Isilkor's autobuildscript handle deenosaurier like just another build slave:

On the git commit hook, autobuild makes deeno build a mac binary with the given git id, e.g. openclonk-mac-{gitid}, pipes the output that deeno gives into a log file and on success, copies the binary via scp onto nosebud into the same place where the other logs and binaries are. This should happen parallel to triggering it's own build slaves for win and linux so autobuild doesn't need to wait for deeno to finish his build. Deeno on the other hand should automatically clean up old binaries (e.g. older than a day) after the build.
This way, we can have mac-autobuilds.
For the development snapshots, nightly just has to be extended to create snapshots not for 4 but 5 different platforms. Thus, the "building the skeleton of a mac app" of deeno is moved to nightly.

Sounds good? Am I overlooking something?

> Do you have a script for that which you could insert into the release scripts?

$ git archive --prefix=openclonk-release-$VERSION-src/ -o openclonk-release-$VERSION-src.tar.gz v$VERSION should work