Feature · archived
Oracle
Oracle Cloud Infrastructure's DevOps service is ending support for Oracle Linux 7 build runners. From 28 August 2026, you can no longer create or run builds on OL7-based build runners in OCI DevOps. This affects the managed CI/CD build service only — it is not the end of the Oracle Linux 7 operating system, which stays on Extended Support until 2028.
left 28 Aug 2026
Quick answers
- Is it true that OCI DevOps ends support for Oracle Linux 7 build runners?
- Yes — and the date has already passed (28 Aug 2026). OCI DevOps is Oracle Cloud Infrastructure's managed CI/CD service, and one of the things it lets you choose is the operating-system image your build pipeline runs on — a "build runner." Oracle is removing Oracle Linux 7 as an option for those build runners.
- When did it take effect?
- 28 Aug 2026 (already passed). Verified against the vendor's own announcement.
- What should I use instead?
- If you use OCI DevOps, audit your build pipelines for any that specify an Oracle Linux 7 build runner and switch them to an Oracle Linux 8 (or newer) runner before 28 August 2026.
What this means for you
OCI DevOps is Oracle Cloud Infrastructure's managed CI/CD service, and one of the things it lets you choose is the operating-system image your build pipeline runs on — a "build runner." Oracle is removing Oracle Linux 7 as an option for those build runners. Its own service-changes notice states plainly: "Effective August 28, 2026, the support for Oracle Linux 7 comes to an end, after which users can't create or run builds on OL7-based build runners." So if you have OCI DevOps build pipelines pinned to an OL7 runner, those builds stop working on 28 August 2026. The scope is worth being precise about, because "Oracle Linux 7 end of support, August 2026" is easy to misread as the whole distribution being retired — it is not. This notice is specifically about the OL7 build-runner image inside OCI DevOps. The Oracle Linux 7 OS itself moved from Premier to Extended Support at the start of 2025 and, per Oracle's Lifetime Support Policy, has Extended Support available into 2028 — so your OL7 servers are not affected by this date; only your OCI DevOps build pipelines are.
Where to go
If you use OCI DevOps, audit your build pipelines for any that specify an Oracle Linux 7 build runner and switch them to an Oracle Linux 8 (or newer) runner before 28 August 2026. Oracle's own guidance in the notice is to migrate to Oracle Linux 8, and it advised doing so early — it flagged that OL7-based build-runner launches would see added latency ahead of the hard cutoff, so treat the 28 August date as the point builds stop, not the point to start planning. This is a build-configuration change, not an application migration: your code and your OL7 servers are untouched; what changes is the OS image your CI/CD builds run on. If your build steps depend on something specific to the OL7 image, test those steps on OL8 as part of the switch.
- Oracle Linux 8 (or newer) build runners in OCI DevOps — the vendor-named replacement image for build pipelines
Oracle is removing Oracle Linux 7 as a build-runner option in OCI DevOps, its managed CI/CD service on Oracle Cloud Infrastructure. Oracle’s own service-changes notice sets the date plainly: “Effective August 28, 2026, the support for Oracle Linux 7 comes to an end, after which users can’t create or run builds on OL7-based build runners.” The change was announced on 27 August 2025 and takes effect a year later.
What this is — and what it is not. A “build runner” in OCI DevOps is the OS image your build pipeline executes on. Oracle is dropping the Oracle Linux 7 image from that list. It is not retiring the Oracle Linux 7 operating system: OL7 moved from Premier Support to Extended Support at the start of 2025 and, under Oracle’s Lifetime Support Policy, Extended Support runs into 2028. The phrase “Oracle Linux 7 end of support, August 2026” reads like the distro dying — but this specific date is about the OCI DevOps build image, not your OL7 servers.
Who is affected. Anyone with OCI DevOps build pipelines configured to use an Oracle Linux 7 build runner. On 28 August 2026 those builds can no longer be created or run.
What to do. Point the affected pipelines at an Oracle Linux 8 (or newer) build runner — Oracle’s named replacement — before the date. Oracle advised migrating early, noting that OL7 build-runner launches would see added latency in the run-up, so the 28 August date is when builds stop, not when to begin. The switch is a build-configuration change rather than an application migration; if a build step relies on something specific to the OL7 image, test it on OL8 as part of the move.
Entry changelog
- — last reviewed.
- — Entry created from Oracle's official OCI "Service changes" documentation (announced 27 August 2025; in effect 28 August 2026). Scope verified as OCI DevOps build runners only, NOT the Oracle Linux 7 OS — OL7 is on Extended Support into 2028 per Oracle's Lifetime Support Policy. Surfaced via Layer-2 discovery; written from Oracle's own notice, not the aggregator that surfaced it.
- — Cutoff date reached. Status set to passed: 28 August 2026 is the stated end of support for OL7-based build runners in OCI DevOps. Date re-verified against Oracle's official OCI service-changes notice the day of the cutoff (still listed). Scope unchanged — this ends the OL7 build-runner option, not the Oracle Linux 7 OS (Extended Support into 2028).
Put this countdown in your README
Building on Oracle? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/oci-devops-oracle-linux-7-eol)Spot an error or a changed date? Tell us and it’s corrected the same night.