That seems reasonable. Thus may add extra time to the build. I had a concern previously on the amount of time some of the build tests takes already (I think during the php tests on large file tests I think). But if that’s not anything of concern then guess it’s not a biggie.
Would the idea be to have ones for the LTS versions and a sample of different distributions then? During the Travis CI build side, there are some Java version specific jobs checks (I think for Java 8 and maybe 15). If there are Java version specific tests already, would it be worth moving those into one of the version specific Java in the matrix? Eric Bresie [email protected] (mailto:[email protected]) > On August 31, 2021 at 7:00:14 AM CDT, Geertjan Wielenga <[email protected] > (mailto:[email protected])> wrote: > Hi all, > > In my clone of Netbeans, I've been experimenting with using a GitHub Action > that will enable us to check that NetBeans still builds successfully after > each pull request that we do -- using a matrix enabling us to set multiple > JDK versions and multiple JDK distros (currently that can only be 'temurin' > and 'zulu'). > > Take a look at it here, I've set it up only for the Linux build: > > https://github.com/geertjanw/netbeans/runs/3472522715 > > What do we think about this? Seems like a logical thing for us to integrate > and it's trivial to do in the workflow that we already have, I'd add a few > extra lines to enable this. > > Thanks, > > Gj
