As of now (if I am wrong Alex please correct me), the following software needs to be installed on Windows slave:
- Visual Studio 2015 Community ( https://www.visualstudio.com/es-es/downloads/download-visual-studio-vs.aspx) with Common Tools for Visual C++ 2015 and Windows 10 SDK. - CMake for Windows (https://cmake.org/download/) - GnuWin32 Patch for Windows ( http://gnuwin32.sourceforge.net/packages/patch.htm) However, Microsoft has begin releasing the Visual C++ Build Tools 2015 (currently as Technical Preview) apart from Visual Studio, targeting precisely build servers. However, I tested them and at least one of the projects requires explicitly the full Visual Studio 2015 to build. I propose to change this CMake behaviour so Visual Studio is not longer necessary to perform the build. For this, I have created the issue https://issues.apache.org/jira/browse/MESOS-5154. Do you think we should wait until we have enabled building with Visual C++ Build Tools instead of asking for install Visual Studio on build slaves? On 8 April 2016 at 00:34, Vinod Kone <[email protected]> wrote: > If you or Alex can let me know what needs to be pre-installed on windows > jenkins slaves, I can file a ticket w/ ASF INFRA and request them to get > those installed. > > On Thu, Apr 7, 2016 at 12:31 AM, haosdent <[email protected]> wrote: > > > https://builds.apache.org/computer/windows1/systemInfo and > > https://builds.apache.org/computer/windows2/systemInfo are windows > > servers. > > But I think they need install Visual Studio 2015 and CMake to build Mesos > > Agent. > > > > On Thu, Apr 7, 2016 at 3:23 PM, Juan Larriba <[email protected]> wrote: > > > > > Hi guys, > > > > > > in order to integrate the Windows builds in the CI cycle to avoid > someone > > > inadvertently breaking the Windows build, a Windows Jenkins slave would > > be > > > necessary. > > > > > > Does the Apache Jenkins currently have a Windows build slave? Has the > > > Windows build enough importance for this kind of questions to be > > > considered? > > > > > > > > > > > -- > > Best Regards, > > Haosdent Huang > > >
