This repository has been archived by the owner on Oct 14, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 33
Adding a new build variant
Martijn Verburg edited this page Apr 6, 2018
·
4 revisions
There are several steps required to add a new variant to build in ci.adoptopenjdk.net and be published on the website:
- Create an issue in the TSC asking to have your variant added. Please add which platforms you'd like supported, which versions of OpenJDK and what level of testing you'd like (jtreg + extras and or system tests and/or TCK/JCK tests).
You typically need to create two new repositories for storing nightly builds and release builds. Some experimental variants like the amber forest from OpenJDK only need nightly builds.
- Create a releases repo using this link naming it
openjdk{version}-{variant}-releases
(e.gopenjdk8-openj9-releases
). - Create a nightly repo using this link naming it
openjdk{version}-{variant}-nightly
(e.gopenjdk8-openj9-nightly
). - On both of these newly created repos navigate to Settings, Collaborators and teams and add the GetOpenJDK team as Admin.
- To start polling the repo to check for new releases add a new block of code with your release details here.
- Add a variant to the website config.json file here.
- Add a variant to the api Wiki here.
- Navigate to the job config here. If you don't have access ensure that you are logged in. You may also need to request access from an org owner.
- Modify the VERSION Choice parameter to add your new variant
- Add a new Conditional Step (single) for your variant. (See other variants for the correct values)
- Add a new line to the job here to gather download statistics for your variant.
You need to have Pipeline create / edit privileges for this.
TODO add details here. Contact gdams for information.