Using integrated cache in actions/setup-java

[litetex]

What is it?

• Bugfix (user facing)
• Feature (user facing)
• Codebase improvement (dev facing)
• Meta improvement to the project (dev facing)

Description of the changes in your PR

Using integrated cache in actions/setup-java instead of specifying it.
See https://github.com/actions/setup-java#caching-gradle-dependencies for details.

Advantages:

• Results in more compact and easier readable code
• We don't need to specify/manage the cache ourselves as the action does it automatically

A test of the above can be seen in:

• https://github.com/litetex/NewPipe/runs/3450616944?check_suite_focus=true
• https://github.com/litetex/NewPipe/runs/3450662800?check_suite_focus=true

APK testing

The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR.

Due diligence

• I read the contribution guidelines.

[Stypox]

Looks good to me, thanks :-)

A test of the above can be seen in:

If I understand correctly the first link is the first run, so there is no cache and it takes 5:30min; the second link is the second run, that has the cache from the first one, so it takes 2min less. Am I right?

[TobiGr]

Looks good.

The API 29 test does not seem to benefit from using the cache, but hey, that thing is buggy all the time xD

[litetex]

@Stypox
Yes this was the cache:

As seen on the left downloading / setting up until :runCheckstyle is executed takes ~1m 30s while on the right (with cache) it's just ~20s

Should have been the case also before I changed it 😄

@TobiGr
https://github.com/litetex/NewPipe/runs/3450662901?check_suite_focus=true says Cache restored successfully (in step "set up JDK 8") so I guess it worked 😄