As we conclude our 2025 reporting cycle, the Project Management Committee (PMC) assessed the many contributions across the Adoptium projects. This report highlights key technical milestones from 2025 Q4 in release automation, testing efficiency, and supply chain integrity.
Release Delivery Goals: 12-Hour Linux Turnaround
A primary objective in Q4 was to reduce the delay between the availability of General Availability (GA) tags and the publishing of platform-specific Temurin binaries. Having assessed through retrospective activities that delays were happening within the compliance testing efforts, focus was put on addressing compliance pipeline-related issues. By stabilising "arctic" recordings for Linux platforms within the dev.jck jobs, the project was able to deliver several Linux platforms within 12 hours of GA tag availability, where the previous delivery goals were between 2 and 7 days.
- Key Contributors: Antonio Vieiro and David Sladky, with guidance from Andrew Leonard.
- The Impact: This reduction in lead time ensures more rapid delivery of security and feature updates to the Linux ecosystem.
Testing Infrastructure: Targeted Reruns and Public Triaging
To optimise resource utilisation within the Temurin Compliance project, the testing framework was updated to allow for more granular test execution.
- Engineering Optimisation: Sophia Guo and Andrew Leonard implemented logic in the AQAvit test framework to rerun only failed arctic test cases rather than entire test targets. This work could then be leveraged by the Temurin Compliance project to significantly lower infrastructure use and compute costs and also reduce the time required to verify that Temurin builds are TCK compliant. Issue: Extend the 'Rerun failed testcases' feature to arctic targets aqa-tests#6756, PRs: Parsing regular expression for arctic TKG#779 and Extended the rerun failed testcases feature to arctic aqa-tests#6757 and Update Arctic runtests.sh to handle multiple ARCTIC_GROUPS for "custom" aqa-tests#6818
- Pipeline Accessibility: The quarter also marked the full-scale deployment of remote trigger rerun links for the public AQA_Test_Pipeline, in other words, allowing people external to the private Temurin Compliance project to remotely trigger and re-trigger automated compliance pipelines. This enables a broader range of contributors to participate in triaging without requiring internal infrastructure permissions. PRs: (Add retrigger public aqa_test_pipeline link ci-jenkins-pipelines#1235 and Enable aqaTestPipeline as a RELAY to remote trigger private aqaTestPipeline aqa-tests#6395)
Infrastructure: Dynamic Provisioning for AQAvit Test Pipelines
To manage the high load during release cycles, the build environment was migrated toward a more elastic model.
- Scaling: Stewart Addison and George Adams enabled AQA testing in containers on Linux/x64 dynamically provisioned Azure VMs. PR: Utilise containers in Azure dynamic VMs for AQA runs aqa-tests#6553.
- Operational Outcome: While the AQAvit test pipelines already supported dynamic agents, they had not been enabled on the Linux/x64 platform. This enablement ensured that the public Jenkins server remained responsive during the high-traffic October release, removing queue times for this platform completely.
Strengthening the Software Supply Chain
The PMC continues to prioritise the integrity and predictability of our installers. In Q4, Scott Fryer addressed a non-determinism issue in the Temurin Debian packaging process. Issue: jpackage works on Zulu but not on Temurin installer#1274 PR: Fix Temurin Debian packages to be non-deterministic. installer#1277
- Technical Fix: By hardening the packaging logic to be deterministic, we eliminated potential configuration inconsistencies
- Downstream Impact: This fix ensures a stable installation path for users and downstream projects, such as Lucene and JavaFX, that depend on consistent package behaviour.
Closing Summary
The technical health of Adoptium relies on our contributors, through the quality of their work and their dedication to fixing the ‘right things’.
The PMC recognises all contributions, including optimising pipelines, resolving installer bugs, or providing technical mentorship. These highlighted achievements of Q4 2025 have established a rigorous baseline for our 2026 roadmap.
While the 2025 Q4 contributions of Antonio, David, Andrew, Sophia, Scott, Stewart, and George have been highlighted, we thank the entire community for their commitment to the technical excellence of Eclipse Adoptium and look forward to celebrating many future achievements.
Looking to make an impact? We’re always looking for new contributors to help shape the future of open-source Java. Whether you’re interested in development, testing, or documentation, your expertise can help us continue to deliver high-quality runtimes to millions. Visit our Contributing page to learn how you can get involved and join our mission today.