Review mirroring behavior for CSPUs

[jiekang]

OpenJDK may now have CSPUs every month. The mirror scripts may need adjustment for this. Information is recorded below for consideration.

Tag/branch behavior (data gathered on 2026-08-21):

Curiously, 17u, 21u and 25u have tags on master and release branch. 8u and 11u only have tags on release branch. 26u does not have a separate branch.

openjdk/jdk26u: 26.0.2.1

branches: none
tags: jdk-26.0.2.1+1, jdk-26.0.2.1-ga

openjdk/jdk25u: 25.0.4.1

branches: jdk25.0.4.1
tags: jdk-25.0.4.1+1, jdk-25.0.4.1-ga, jdk-25.0.5+3

openjdk/jdk21u: 21.0.12.1

branches: jdk21.0.12.1
tags: jdk-21.0.12.1+1, jdk-21.0.12.1-ga, jdk-21.0.13+3

openjdk/jdk17u : 17.0.20.1

branches: jdk17.0.20.1
tags: jdk-17.0.20.1+1, jdk-17.0.20.1-ga, jdk-17.0.21+3

openjdk/jdk11u : 11.0.32.1

branches: jdk11.0.32.1
tags: jdk-11.0.32.1+1, jdk-11.0.32.1-ga

openjdk/jdk8u : 8u503

branches: openjdk8u504
tags: jdk8u504-b01, jdk8u504-ga

[jiekang]

Summary ( Bob Assisted ) of the Issues with the JDK8 Mirror tags issue..

FYI @smlambert / @andrew-m-leonard

JDK 8u504 (CPU) Release Tag Fix

Adoptium Temurin · August 2026 · release-openjdk8-pipeline

---

Background

The August 2026 CPU (Critical Patch Update) for JDK 8 is jdk8u504-b01. The Adoptium release pipeline (release-openjdk8-pipeline) was failing at run #127 with a README.JAVASE missing error, preventing the Temurin build from completing.

---

Root Cause Analysis

1. Bad jdk8u504-b01_adopt tag in adoptium/jdk8u

The _adopt tag pointed directly at the raw upstream commit 4efe3643 — identical to jdk8u504-b01 itself — with no Adoptium merge commit on top. This meant README.JAVASE (the Temurin marker file required by sbin/prepareWorkspace.sh) was absent, causing an immediate exit 1.

2. Why skaraMirror.sh couldn't auto-fix it

The script uses git tag --merged origin/master to find upstream tags to mirror. jdk8u504-b01 exists only on the openjdk8u504 side branch of openjdk/jdk8u (Skara) and was never merged into master — upstream went straight from 502 to 512. So the mirror script silently skipped it every run.

3. Stale cached tags in Jenkins workspace

The git-skara-jdk8u mirror job had the bad _adopt tags cached locally and re-pushed them on each run, perpetuating the problem. The workspace was wiped to stop this.

4. adoptium/alpine-jdk8u — separate repo, same problem

The Alpine Linux x64 platform builds from a completely separate repository. This repo also had no jdk8u504-b01_adopt tag at all, which wasn't discovered until pipeline run #128 when the other 6 platforms were already building successfully.

---

Fix 1 — adoptium/jdk8u

Result: jdk8u504-b01_adopt → 1358e1b2

# Delete the bad tag from the remote
GIT_SSH_COMMAND="ssh -i ~/.ssh/id_ed25519_github -p 443" \
  git push git@ssh.github.com:adoptium/jdk8u.git \
  :refs/tags/jdk8u504-b01_adopt

# Clone the repo and configure identity
cd /tmp && git clone https://github.com/adoptium/jdk8u.git jdk8u-fix
cd jdk8u-fix
git config user.email "steelhead31@users.noreply.github.com"
git config user.name "steelhead31"

# Fetch the 504 side branch from the Skara upstream
git remote add skara https://github.com/openjdk/jdk8u.git
git fetch skara refs/heads/openjdk8u504:refs/remotes/skara/openjdk8u504

# Reset to the last good _adopt tag as the base
git reset --hard jdk8u502-b07_adopt   # d9b9e48a "Merging jdk8u502-b07 into release"

# Merge the upstream 504 tag — README.JAVASE comes from the base
git merge --no-ff jdk8u504-b01 -m "Merging jdk8u504-b01 into release"

# Verify README.JAVASE is present
ls README.JAVASE

# Tag and push
git tag jdk8u504-b01_adopt HEAD
GIT_SSH_COMMAND="ssh -i ~/.ssh/id_ed25519_github -p 443" \
  git push git@ssh.github.com:adoptium/jdk8u.git \
  refs/tags/jdk8u504-b01_adopt

---

Fix 2 — adoptium/alpine-jdk8u

Result: jdk8u504-b01_adopt → f8624881

# Clone the alpine repo and configure identity
cd /tmp && git clone https://github.com/adoptium/alpine-jdk8u.git alpine-jdk8u-fix
cd alpine-jdk8u-fix
git config user.email "steelhead31@users.noreply.github.com"
git config user.name "steelhead31"

# Reset to the last good _adopt tag as the base
git reset --hard jdk8u502-b07_adopt   # 513a8933 "Merging jdk8u502-b07 into release"

# jdk8u504-b01 is already present in this repo (mirrored upstream tag)
# Merge it — clean, no conflicts
git merge --no-ff jdk8u504-b01 -m "Merging jdk8u504-b01 into release"

# Verify README.JAVASE is present
ls README.JAVASE

# Tag and push
git tag jdk8u504-b01_adopt HEAD
GIT_SSH_COMMAND="ssh -i ~/.ssh/id_ed25519_github -p 443" \
  git push git@ssh.github.com:adoptium/alpine-jdk8u.git \
  refs/tags/jdk8u504-b01_adopt

---

Pipeline Runs

Run	Trigger	Outcome
#127	Automated (releaseTrigger_jdk8u)	❌ FAILURE — README.JAVASE missing on all platforms
#128	Automated (after Fix 1)	❌ FAILURE — 6/7 platforms OK; Alpine x64 failed (no tag in alpine-jdk8u)
#129	Manual (alpine x64 only, after Fix 2)	✅ SUCCESS — jdk8u-release-alpine-linux-x64-temurin #49 passed

---

Key Technical Facts

• jdk8u504-b01 commit 4efe3643 is on the openjdk8u504 side branch of openjdk/jdk8u (Skara) — never merged into master. Upstream went straight 502 → 512.
• The README.JAVASE check is in temurin-build/sbin/prepareWorkspace.sh — causes exit 1 if absent.
• Both adoptium/jdk8u and adoptium/alpine-jdk8u are independent repos and each required their own jdk8u504-b01_adopt merge tag.
• The correct _adopt tag pattern: merge commit, parent 1 = previous _adopt tag (502-b07_adopt), parent 2 = upstream CPU tag (504-b01), with README.JAVASE present at HEAD.
• jdk8u512-b01_adopt was already present in both repos (October release), so the gap was solely the missing 504 tags.

---

Remaining Note

The git-skara-jdk8u mirror job will encounter the same situation for any future CPU release whose tag lands on a Skara side branch rather than master. The manual merge approach will need to be repeated, or skaraMirror.sh will need a fix to handle side-branch tags.

---

Outcome

All platform builds for jdk8u504-b01 are complete. Alpine x64 (#49) confirmed SUCCESS. Pipeline release-openjdk8-pipeline #128 covers the remaining 6 platforms; #129 is the definitive alpine run.

Originally posted by @steelhead31 in #295

[jiekang]

For jdk8u compared to jdk11u+,

Scott's fix merged jdk8u504 into the release branch. The other versions have separate branches, like release_jdk-11.0.32.1.

Unclear what implications this has for current or future releases.

The equivalent separate branch exists in 8 as release_jdk8u504, but does not contain the merge commit which would add README.JAVASE file. Perhaps the fix should have been in that branch.

[andrew-m-leonard]

For jdk8u compared to jdk11u+,

Scott's fix merged jdk8u504 into the release branch. The other versions have separate branches, like release_jdk-11.0.32.1.

Unclear what implications this has for current or future releases.

The equivalent separate branch exists in 8 as release_jdk8u504, but does not contain the merge commit which would add README.JAVASE file. Perhaps the fix should have been in that branch.

hmm, possibly, let me check with Andrew Hughes

[andrew-m-leonard]

I am going to add Adoptium mirror support for update branches, the skaraMirror.sh basically partially supports it, since the jdk(head) repo has "feature branches", which in essence is the same thing. It should be just a matter of calling skaraMirror.sh with the "update branch", and a few small changes to skaraMirror.sh.
I am tempted to change the mirror jobs to use a JenkinsFile as well, rather than hard coded jenkins "Build Step" scripts in each job that needs maintenance...

[andrew-m-leonard]

Upstream openjdk repo branches and tags summary:

• jdk8u:
  • branch: openjdk8u504 : Tagged jdk8u504-b01
• jdk11u:
  • branch: jdk11.0.32.1 : Tagged jdk-11.0.32.1+1
• jdk17u:
  • branch: jdk17.0.20.1 : Tagged jdk-17.0.20.1+1
• jdk21u:
  • branch: jdk21.0.12.1 : Tagged jdk-21.0.12.1+1
• jdk25u:
  • branch: jdk25.0.4.1 : Tagged jdk-25.0.4.1+1
• jdk26u:
  • branch: master : Tagged jdk-26.0.2.1+1

[andrew-m-leonard]

Adoptium mirror repo branches and tags summary:

• jdk8u:
  • branch: release : Tagged jdk8u504-b01_adopt
• jdk11u:
  • branch: release_jdk-11.0.32.1 : Tagged jdk-11.0.32.1+1_adopt
• jdk17u:
  • branch: release_jdk-17.0.20.1 : Tagged jdk-17.0.20.1+1_adopt
• jdk21u:
  • branch: release_jdk-21.0.12.1 : Tagged jdk-21.0.12.1+1_adopt
• jdk25u:
  • branch: release_jdk-25.0.4.1 : Tagged jdk-25.0.4.1+1_adopt
• jdk26u:
  • branch: release : Tagged jdk-26.0.2.1+1 _adopt