Cache Gradle dependency cache to speed up CI

[glefloch]

This leverage github action to cache gradle dependencies and downloading everything on each run

[gsmet]

Cool idea. I added a small suggestion inline. I wouldn't do that for the existing cache now but we could experiment with this for the newly added one.

[gsmet]

Just an idea but maybe we could try to use the cache feature integrated in setup-java@v3? More details here: https://github.com/actions/setup-java#caching-packages-dependencies

[glefloch]

I updated the branch using the setup-java@v3

[famod]

Gradle is also running in the initial build, no? Might be beneficial there as well. But I guess the keys should be different then because I guess the gradle run in the initial build pulls in fewer dependencies than in the test job?

[famod]

This is what I mean, from the initial build:

2022-06-16T19:51:05.3507692Z [INFO] Quarkus - Maven Plugin ............................. SUCCESS [  7.282 s]
2022-06-16T19:51:05.3508108Z [INFO] Quarkus - Gradle Plugin - Parent ................... SUCCESS [  0.047 s]
2022-06-16T19:51:05.3508595Z [INFO] Quarkus - Gradle Model ............................. SUCCESS [01:22 min]
2022-06-16T19:51:05.3509018Z [INFO] Quarkus - Gradle Plugin ............................ SUCCESS [ 39.042 s]
2022-06-16T19:51:05.3509448Z [INFO] Quarkus - Extension Gradle Plugin .................. SUCCESS [ 37.329 s]
2022-06-16T19:51:05.3509886Z [INFO] Quarkus - Command Line Interface ................... SUCCESS [ 10.434 s]
2022-06-16T19:51:05.3510315Z [INFO] Quarkus - Integration Tests ........................ SUCCESS [  0.053 s]

[gsmet]

Let's try that and see how it goes.

[gsmet]

I rebased to drop the merge commit btw.

[quarkus-bot]

Failing Jobs - Building a944859

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/resteasy-reactive/rest-client-reactive-jaxb/deployment 

📦 extensions/resteasy-reactive/rest-client-reactive-jaxb/deployment

✖ io.quarkus.rest.client.reactive.jaxb.test.SimpleJaxbTest.shouldConsumePlainXMLEntity - More details - Source on GitHub

org.jboss.resteasy.reactive.ClientWebApplicationException: Received: 'Internal Server Error, status code 500' when invoking: Rest Client method: 'io.quarkus.rest.client.reactive.jaxb.test.SimpleJaxbTest$XmlClient#plain'
	at org.jboss.resteasy.reactive.client.impl.RestClientRequestContext.unwrapException(RestClientRequestContext.java:170)
	at org.jboss.resteasy.reactive.common.core.AbstractResteasyReactiveContext.handleException(AbstractResteasyReactiveContext.java:317)

✖ io.quarkus.rest.client.reactive.jaxb.test.SimpleJaxbTest.shouldConsumeXMLEntity - More details - Source on GitHub

org.jboss.resteasy.reactive.ClientWebApplicationException: Received: 'Internal Server Error, status code 500' when invoking: Rest Client method: 'io.quarkus.rest.client.reactive.jaxb.test.SimpleJaxbTest$XmlClient#dto'
	at org.jboss.resteasy.reactive.client.impl.RestClientRequestContext.unwrapException(RestClientRequestContext.java:170)
	at org.jboss.resteasy.reactive.common.core.AbstractResteasyReactiveContext.handleException(AbstractResteasyReactiveContext.java:317)

[glefloch]

Thanks, I missed it.

[glefloch]

I don't think failure is related, right ?

[famod]

I don't think so. That test failed in another PR of mine in a similar way.