On Tue, Nov 12, 2013 at 3:25 PM, Nate Finch <[email protected]> wrote: > Are we compiling the client for Windows and OSX during CI? That's one huge > deficiency we have right now is that we have completely separate OSes that > we don't even try to compile on until release day. It would be nice to get > notified earlier of compilation failures, at the very least.
Not yet. We are specifically testing precise amd64. testing hombrew and win are additional dimension. ARM and i386 are similar > Note that cross-OS compilation with Go is really easy, so you can still run > the build for both on Linux. Obviously, that won't test that the binaries > actually work, but we'll know they compile at least, which is a pretty > important step. The ARM may be in the case you outline. We built the packages for 1.16.3, but we only had genuine confirmation that they compiled. In the case of homebrew (OS X) we want to verify our tarball is compatible with XCode + homebrew's gcc and go. The formula has broken in the past so I now do the building locally before requesting a pull. I think ARM testing may be like the homebrew case where we want a reference platform to build and test with. -- Curtis Hovey Canonical Cloud Development and Operations http://launchpad.net/~sinzui -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
