Update README and add Java 8, 11, 16 Temurin Debian, Red Hat and Suse

[karianna]

• Update gitignore
• Update README.md to reflect how scripts work today
• First cut of Java 8 Temurin Debian files

[karianna]

@aahlenst - Would it be OK for you to review this PR and see if it makes sense to you? It's still a WIP but I want to make sure I'm heading in roughly the right direction here :-)

[karianna]

I need to get an RPM-based VM now don't I. Anything you'd recommend for me to spin up simply in VirtualBox (yeah, yeah I should be Docker pro here but I'm a dinosaur and still like my VMs)

[aahlenst]

@karianna Will do, give me a couple of days.

[aahlenst]

The list of tools included in the JDK can for example be pulled from https://github.com/adoptium/installer/blob/master/linux/deb/config/jdk-8-hotspot/tools.txt. Might need an update if OpenJDK added or dropped tools lately. Lack of pack200 stood out, for example.

[aahlenst]

I suppose the spec file for Suse comes at a later stage?

[aahlenst]

I need to get an RPM-based VM now don't I. Anything you'd recommend for me to spin up simply in VirtualBox (yeah, yeah I should be Docker pro here but I'm a dinosaur and still like my VMs)

For final verification of the package, why not. But you can run the build incl. tests on any computer running Linux or even on a Mac as long as you have both Docker and a JDK. That already catches a ton of errors.

[karianna]

I suppose the spec file for Suse comes at a later stage?

Yes, once I'm confident with Debian and RH :-)

[karianna]

@aahlenst Thanks for the detailed review, I've updated everything except for the RPM spec file (I need to still update the tools there).

[sxa]

I haven't reviewed all of it yet, but here are a small number of initial comments

[sxa]

One suggestion to make a clarification in a comment in the code based on the responses to my feedback, but otherwise seems good.

[gdams]

Test failures CC @karianna @aahlenst

[karianna]

Yeah, I've posted in the issue tracking this. It's a file size difference and I'm really not sure if its a test data issue here.

[jerboaa]

This seems fine for an initial cut.

[karianna]

@aahlenst I can't figure out why the ZypperTests fail intermittently. Running those checks locally always passes for me. https://github.com/adoptium/installer/runs/3543407221?check_suite_focus=true is an example of the failure

[aahlenst]

For easier analysis of test failures in CI it's best to collect Gradle's reports. Something like:

- uses: actions/upload-artifact@v2
  if: failure()
  with:
    name: gradle-reports
    path: |
      linuxNew/**/build/reports

Gradle captures stdout and stderr, so we should see the output of Zypper and other tools.

[karianna]

Looks like potentially fixing up the hkps access for keys has resolved the last of the issues.