On 7/2/19 10:25 AM, Robert Varga wrote: > what is our situation for JDK12/13 support on slaves? Can we get at > least 12 supported?
The build instances get java installed via the following Ansible Galaxy role: lfit.java-install Which is managed out of [0] and mirrored to [1]. There's three ways going forward to get additional JDKs defined: 1) Propose a Gerrit change with it yourself 2) Open a issue in the RELENG Jira board against component common-packer and it will end up in the backlog and either eventually picked up by LFRE or someone in the community 3) Open a support issue as per [2] and LFRE will either work the issue right away or essentially do #2 but likely pick up that card right away There is, however, one final step after the build instances get it defined, and that's to actually tell Jenkins about it. That would be a service desk request but it's only workable until the ansible role has been updated. A note on the Ansible roles: The change just has to get merged before a packer run happens for it to be picked up, while the Ansible roles are all versioned, we haven't cut one in a very long time since none of our Packer definitions use a specific version and by default Ansible Galaxy just uses whatever is available at the repo master HEAD if no version is specified. -Andy- [0] https://gerrit.linuxfoundation.org/infra/admin/repos/ansible/roles/java-install [1] https://github.com/lfit/ansible-roles-java-install [2] https://docs.releng.linuxfoundation.org/en/latest/helpdesk.html -- Andrew J Grimberg Manager Release Engineering The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
