GitHub build and test action

[Paul King <pa...@asert.com.au>]

Hi folks,

I was thinking of splitting the build and test GitHub action into 2 -
probably giving a suffix of "main" and "aux".

Currently, we have java versions: [11, 12, 13, 14, 15, 16, 17, 18]
and we run those tests on "push" and "pull_request".

I was basically going to move 12 through 16 into the "aux" action and
only run those for "push".

The pros are it would speed up feedback - there is frequently a queue
while jobs get processed.

The cons are there might be rare PRs where we don't catch issues with
those non-LTS JDK versions until merge time.

Thoughts?

Cheers, Paul.

Re: GitHub build and test action

[Peter Burka <Pe...@twosigma.com>]

I don't think Groovy is obliged to support those already-out-of-support JDKs. I think the risk is quite low, and that this makes sense.

/peter
________________________________
From: Paul King <pa...@asert.com.au>
Sent: Friday, October 28, 2022 6:49 AM
To: Groovy_Developers <de...@groovy.apache.org>
Subject: GitHub build and test action

Hi folks,

I was thinking of splitting the build and test GitHub action into 2 -
probably giving a suffix of "main" and "aux".

Currently, we have java versions: [11, 12, 13, 14, 15, 16, 17, 18]
and we run those tests on "push" and "pull_request".

I was basically going to move 12 through 16 into the "aux" action and
only run those for "push".

The pros are it would speed up feedback - there is frequently a queue
while jobs get processed.

The cons are there might be rare PRs where we don't catch issues with
those non-LTS JDK versions until merge time.

Thoughts?

Cheers, Paul.