mirror of
https://github.com/adoptium/temurin-build.git
synced 2026-10-05 22:04:36 +02:00
Page:
Creating new jdkNNu (updates) repro mirror from the jdkNN release mirror
Pages
A Conversation about versions and setting them in build configuration
Building OpenJDK using temurin build scripts within the adopt build docker container
CPU and or PSU Levels we build to
Creating new jdkNNu (updates) repro mirror from the jdkNN release mirror
Differences between Adopt OpenJDK binaries and Oracle JDK Binaries
Eclipse Temurin Windows Visual Studio, Toolset, SDK and ReDist versions
Getting Started...
Home
How to create a "reproducible build" on a Linux OS
Other OpenJDK Build Efforts to integrate
Outreachy: Secure Software Supply Chain Enhancements: Project RASPberry
Outreachy: Software Bill Of Materials Refinements: Project SmoothBOM
Release proposal for OpenJDK for Eclipse OpenJ9 binaries at AdoptOpenJDK.
Resolving Skara mirror job "Merge Conflicts"
Setting up new build jobs, mirrors,... when a new openjdk version is branched from jdk(head)
Step‐by‐step: Temurin reproducible verification instructions for Windows x64
Temurin 3rd Party Reproducible Verification Guides
Temurin Release Guide
Temurin reproducible verification instructions for building current Windows ReDist DevKit DLL package (vs2022_redist_14.40.33807_10.0.26100.1742)
Temurin reproducible verification instructions for setting up a new Windows machine with the current required VS2022 toolchain (Visual Studio 2022 LTSC 17.12.12)
[WIP] Minimum OS levels
No results
NOTE: THIS PAGE IS NOW SUPERCEDED BY https://github.com/adoptium/temurin-build/wiki/Setting-up-new-build-jobs,-mirrors,...-when-a-new-openjdk-version-is-branched-from-jdk(head)
When and why?
When a new jdk release is created upstream eg.jdk-19, a new upstream repo is branch from jdk(head), so https://github.com/openjdk/jdk19, this is then mirrored to https://github.com/adoptium/jdk19. Once shipped upstream moves to development of updates for the following .0.N updates, this is done in a new repro https://github.com/openjdk/jdk19u, known as the "updates" repo. We need to create a new mirror for this "updates" repo after the initial release has been shipped.
How?
- Pre-req: You must have "write/push" access to the jdkNN github repositories.
- Create the new mirror jdkNNu repository using otterdog: https://github.com/adoptium/.eclipsefdn Create a new PR for file https://github.com/adoptium/.eclipsefdn/blob/main/otterdog/adoptium.jsonnet and add a definition like this (Sample PR). If creating a jdkNNu, also archive the origin jdkXX release (Sample PR):
newMirrorRepo('jdkNNu') {},
Steps 3-6 are no longer required to be run manually and the first run of the [skara mirror jobs](https://ci.adoptium.net/job/git-mirrors/job/adoptium/) should populate the repository
- Duplicate the jdkNN mirror to the new jdkNNu mirror repository:
git clone --bare https://github.com/adoptium/jdkNN
cd jdkNN.git
git push --mirror git@github.com:adoptium/jdkNNu.git
- Clone mirror-scripts locally:
git clone git@github.com:adoptium/mirror-scripts.git
cd mirror-scripts.git
- Run skara mirror script to update the new jdkNNu mirror to the latest upstream "updates" repository:
./skaraMirror.sh jdkNNu
Resolve any conflicts if needed.
- Rename the existing skara mirror job jdkNN to jdkNNu:
- Rename existing job https://ci.adoptopenjdk.net/view/git-mirrors/job/git-mirrors/job/git-skara-jdkNN/
- Name git-skara-jdkNNu, also edit Build->Execute shell command to call:
bash ./skaraMirror.sh jdkNNu
- Then follow instructions here for updating the pipeline job generators, but use jdkNNu instead of jdkNN: https://github.com/adoptium/temurin-build/wiki/Setting-up-new-build-jobs,-mirrors,...-when-a-new-openjdk-version-is-branched-from-jdk(head)#create-pipeline_jobs_generator_jdknn-job-and-configuration