11-08-2019, 12:50 AM
(11-07-2019, 07:00 PM)xoft Wrote: Appveyor already builds Cuberite using VS2017 as part of PR checking, it's just a bit slow ( https://github.com/cuberite/cuberite/issues/4378 ) The major task is now to make Appveyor send the built binaries to our Jenkins (or other presentable download page).I think the best idea would be to update the Windows download links on Cuberite's homepage to the Appveyor links (which would be https://ci.appveyor.com/api/projects/mad...nch=master and https://ci.appveyor.com/api/projects/madmaxoft/mcserver/artifacts/Cuberite.zip?job=Windows-x64&pr=false&branch=master after a merge to the main repo), and possibly set up a 301 redirect from the old URLs (https://builds.cuberite.org/job/Cuberite...berite.zip and https://builds.cuberite.org/job/Cuberite...berite.zip) to the new ones. As far as I'm concerned, linking Appveyor with our Jenkins server isn't trivial, and would only waste the build server's bandwidth. The average user will download builds from the homepage in any case.