On 11/20/14, 8:30 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > for some of our builds which require tests, we need a Windows machine, I >can't remember for sure but I think we used one from builds.apache.org, >can't remember what was the problem with, can someone refresh my memory ?
Yes, we tried using the Windows slave on builds.a.o. After spending way too much time begging Infra to install and configure custom things we needed and then having them choose versions of Jenkins that busted our builds, we switched to using my VM at apacheflexbuilds.cloudapp.net and have had very few issues since. It does not make sense to me to share a Windows build machine with other projects that may have conflicting needs for versions of dependencies. And there was no way I could have logged into builds.a.o and debug over RDP some problem where a test only failed on the build machine. So, IMO, we don’t want to have builds.a.o try to run scripts that do GUI tests, but even Squiggly really should have GUI tests some day. Is it possible that the “build” that runs on builds.a.o does not compile source code or runs tests, but instead grabs artifacts from apacheflexbuilds and packages things? Or I suppose it could grab a known good source package from apacheflexbuilds and then run against that and skip tests. Thoughts? -Alex
