This issue lists things that we need to do to fully migrate to the new CI. * [ ] Confirm that the new [release CI job](https://ci.trustedfirmware.org/view/Mbed-TLS/job/mbedtls-restricted-release-new/) has feature parity to the [internal release testing job](https://jenkins-mbedtls.oss.arm.com/job/mbedtls-release-new/). * [ ] Test the new [release CI job](https://ci.trustedfirmware.org/view/Mbed-TLS/job/mbedtls-restricted-release-new/) and confirm that we can make an emergency release if needed --- * [x] Trial period where the new CI runs in parallel with the old one on pull request and nightlies * [x] Have a name that isn't “new CI” * Current plan: switch the new CI to the existing name ("TF OpenCI: PR tests" and "TF OpenCI: Interface stability tests"), and switch the Linaro CI to a different name "TF OpenCI (legacy): PR tests" and "TF OpenCI (legacy): Interface stability tests". * [x] [Adapt Groovy scripts](https://github.com/Mbed-TLS/mbedtls-test/issues/225) → https://github.com/Mbed-TLS/mbedtls-test/pull/218 * [ ] [Update developer guide](https://github.com/Mbed-TLS/mbedtls-test/issues/225) * [ ] Update Arm internal documentation * [x] Adapt `mbedtls-kick-ci` → https://github.com/Mbed-TLS/mbedtls-docs/pull/190 * [x] Adapt [CI stats (health) script from @mpg](https://github.com/Mbed-TLS/mbedtls-test/pull/185) * [x] Switch the required check all protected branches from the current CI (Linaro OpenCI) to the new one * Switched to "New CI (testing): PR tests" on 2025-11-03 ~17:00 * [x] Trial period where the new CI does the merge queues * [ ] Switch the [`www.trustedfirmware.org` test system dashboard](https://github.com/TrustedFirmwareWebsite/website/blob/main/fetch_dashboard_data.py) * [ ] Migrate the previous persistent release artifacts from the mbedtls-release-new