I guess you have your own infrastructure but you can freely build open source projects with Github actions. They provide Linux, Windows, and Mac.
At bndtools we build on all. A few years ago we started to build on Windows for similar reasons you seem to experience now. It took us a number of months to work out all the bugs, there were quite a few. Confirming my prejudices against Windows over and over again :-) Building with Github actions is frighteningly easy, you can look at the bnd build for an example. We build on many different Java versions and platforms. https://github.com/bndtools/bnd/blob/master/.github/workflows/cibuild.yml <https://github.com/bndtools/bnd/blob/master/.github/workflows/cibuild.yml> Kind regards, Peter Kriens > On 21 Jan 2020, at 09:55, Lars Vogel <lars.vo...@vogella.com> wrote: > > Hi all, > > The test failures are not reproducable on Gerrit nor locally on Linux. > > I will try to setup a Windows machine to see if these are real errors > or only a temporary issue with the Windows test machine. Looking at > the test history of our recent builds, the Windows machine always had > test errors which other machines did not have. > > Anyone knows how to check / rest the Windows test machine? > > Best regards, Lars > > > > On Tue, Jan 21, 2020 at 9:46 AM Andrey Loskutov <losku...@gmx.de> wrote: >> >> Hi, >> >> we had numerous regressions in two last builds, I've opened >> >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559352 >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559353 >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=559355 >> >> And I guess there are more, we just don't see them because our test coverage >> is not the best. >> >> I don't know why should we continue this practice of blind "mass changes" >> for no good reason, that caused so many regressions so far. >> >> My best example of such regression, on which I've spent a full work week of >> my time, was https://bugs.eclipse.org/bugs/show_bug.cgi?id=551147. >> >> I'm tired to spend my time to do house keeping for others, and I don't see >> anyone else doing this work. I don't think this is fair. >> >> I would propose that committers that merge "mass changes" *must* do the work >> I do: >> >> 1) Check SDK build results after integration of mass changes and identify >> new failures >> 2) Report bugs for new failures >> 3) Identify offending commits and notify authors >> >> If this sounds as too much work, I would propose to re-think the "benefit" >> of mass changes. >> If we continue in the same way as today, at some point in time the code is >> "fully optimized" but Eclipse is not usable anymore. >> >> Kind regards, >> Andrey Loskutov >> >> Спасение утопающих - дело рук самих утопающих >> >> https://www.eclipse.org/user/aloskutov >> >> _______________________________________________ >> platform-dev mailing list >> platform-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe from >> this list, visit >> https://www.eclipse.org/mailman/listinfo/platform-dev > > > > -- > Eclipse Platform project co-lead > CEO vogella GmbH > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: > http://www.vogella.com > _______________________________________________ > platform-dev mailing list > platform-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev