Continuous building with Wercker

[schickling]

Wercker is currently still in beta but I use it for almost all my projects as CI provider and even for automatic deployment. It's free at the moment and afaik will always be free for open source projects.

It allows to build docker images and run commands on them. We can even export the docker image.

So my propose would be to use Wercker for continuous building of the binary files.

[riobard]

Unfortunately we have to build on OS X due to the TLS problem (see #13) until we figure out the proper toolchains to cross-compile from Linux.

[schickling]

We could use Saucelabs for that?

[riobard]

We do not have an OS X CI server, so I'm not sure how Saucelabs could help. Mind to explain?

[schickling]

Well it might not be the best solution but we could trigger a script on Wercker for each commit that builds a binary file on a OSX saucelab device. But thats at best a hacky workaround ;)

[riobard]

I'm not sure how Saucelabs work. Reading their website gives me the impression they have some OS X machines that are used to run web app tests in Safari. Do you mean we could use those OS X machines to build Go projects?

[schickling]

As far as I know Travis uses saucelab machines for CI of XCode projects, so it should work.

[riobard]

That's very interesting. @boot2docker/team-cli what do you think?

[gmlewis]

Hmmm... I tried the Go box on the Werker site, but it was empty.
So is this similar to the Zutubi Pulse server that rebuilds your project on
various platforms and notifies you of breakages?
Sounds interesting if so.

[tianon]

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).