UnixPB: Installer role and playbook

[Haroon-Khel]

Ref #1283

Includes a role, installer, which installs the prerequisite build tools for the linux installer job, and a playbook, installer-setup.yml, which runs this role alongside the Jenkins_User and Superuser role to configure machines to be able to execute the Linux installer Jenkins job.

Tested by running Rpm and Deb build tasks, see https://github.com/AdoptOpenJDK/openjdk-installer/tree/master/linux#deb-packages, on a ubuntu 18.04 machine on which the playbook had been run. Build tasks were successful

[Haroon-Khel]

Currently only supports Ubuntu 18.04 on x86

[Willsparker]

Tested on U18 Vagrant VM. Playbook went through fine :-)

[gdams]

Is there a reason that you don't just want to install these dependencies on all our build machines?

creating an additional playbook for this seems like overkill IMO

[karianna]

Is there a reason that you don't just want to install these dependencies on all our build machines?

creating an additional playbook for this seems like overkill IMO

I think it's about using Ansible to be able to replicate installing those dependencies if we lose machines?

[sxa]

@gdams it was more around any signing keys/authentication tokens etc. - while that can be done using jenkins secrets, we're not currently doing that and from a security/paranoia perspective I'm more keen to do this on machines we can keep a bit more locked down.

@karianna I believe George was suggesting adding them into the main build/test playbooks as opposed to objecting to adding this stuff into the playbooks at all.

[Haroon-Khel]

@gdams I included the linux_installer_setup.yml playbook in the case where we need a sole machine for the linux installer Jenkins job, but if its considered overkill I can remove it.
I still feel that it would be convenient to have the role which installs only the linux installer prerequisites, as per #1283 (comment), since this role can be included in the main Unix playbook if needed.

[Willsparker]

@Haroon-Khel I'd agree with having the individual role in the main playbook (personally)- as that would keep consistency with the Windows playbook ( https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/master/ansible/playbooks/AdoptOpenJDK_Windows_Playbook/roles/WiX/tasks/main.yml ).

[sxa]

@Haroon-Khel Have you been able to verify whether a setup done with this playbook is suitable for running all the operations in the install jobs or does that still have to be verified?

[Haroon-Khel]

Ive tested only the gradle tasks buildDebPackage and buildRpmPackage. I wasnt able to test the upload tasks as I do not have access to the artifactory user and password

[sxa]

I'm going to let this one in for now. If we can subsequently look at whether the keys can be made adequately secure then we can revist adding this into the main pipelines, but this is the less risky option for now.