We currently test the SUP with java8 & java11, we should aim for java 17 and only build for this platform.
We want to run in staging for a week or 2 to ensure things are stable.
AC:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| SUP: upgrade Java 17 | operations/deployment-charts | master | +1 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T404340 [EPIC] Upgrade flink jobs to java 17 | |||
| Resolved | pfischer | T404417 Test & upgrade the cirrus-streaming-updater with java 17 |
You can use the docker-registry.discovery.wmnet/flink:1.20.2-wmf1-20250912 image to test flink 1.20 running on Bookworm / JRE 17.
@pfischer just fyi I pushed a quick release to test the current job with the new image, it's running in wikikube@staging.
The image is v20250918195946-a438845 based on https://gitlab.wikimedia.org/repos/search-platform/cirrus-streaming-updater/-/merge_requests/192 that I reverted right after.
Mainly I wanted to see how flink behaved with a job built with java11 but running on a java17 runtime.
This task is about migrating the build of the job itself to java17 itself and using the new image.
pfischer opened https://gitlab.wikimedia.org/repos/search-platform/cirrus-streaming-updater/-/merge_requests/196
Build against Java 17
pfischer merged https://gitlab.wikimedia.org/repos/search-platform/cirrus-streaming-updater/-/merge_requests/196
Build against Java 17
Change #1196470 had a related patch set uploaded (by Peter Fischer; author: Peter Fischer):
[operations/deployment-charts@master] SUP: upgrade Java 17
Change #1196470 abandoned by Ebernhardson:
[operations/deployment-charts@master] SUP: upgrade Java 17
Reason:
This was shipped yesterday with I98978dc23c03429e1b405af4537aba82e3fd8be9
I shipped a SUP update yesterday for T406205 which included this update to java 17. No surprises, everything rolled out cleanly on java 17.