The collaboration addresses a critical gap in enterprise development workflows
The enterprise development landscape has been divided for decades. While cloud-native teams enjoy modern CI/CD pipelines, collaborative workflows, and automated testing environments, their mainframe counterparts have remained trapped in a time warp of legacy tooling and isolated development practices. This week, GitLab and IBM announced a partnership aimed at finally bridging this divide.
The Problem: Two Worlds, One Enterprise
Walk into any large enterprise today, and you’ll likely find a tale of two development teams. The cloud-native developers work with sleek, modern tools-committing code to Git repositories, triggering automated builds, and deploying through sophisticated pipelines. Meanwhile, down the hall, mainframe developers wrestle with decades-old library managers, manual file transfers, and SSH workarounds that would make any security team cringe.
This isn’t just about developer experience-though that’s certainly part of it. The fragmentation creates real business problems. Organizations end up maintaining expensive parallel toolchains, with premium licensing costs for limited legacy functionality. Delivery cycles slow to a crawl. And perhaps most critically, attracting new talent becomes increasingly difficult when half your development stack feels like an archaeological dig.
Katie Norton, Research Manager for DevSecOps and Software Supply Chain Security at IDC, puts it succinctly: “IDC research shows that mainframe developers often work with legacy tooling that contributes to delivery inefficiencies and makes it harder to attract new talent.”
Enter GitLab Ultimate for IBM Z
The new GitLab Ultimate for IBM Z represents more than just another integration-it’s a fundamental rethinking of how mainframe development should work in 2025. At its core, the solution provides native z/OS Runner support, allowing CI/CD pipelines to execute directly on mainframe infrastructure without the security risks and complexity of remote connections.
But the real innovation lies in the unified approach. Developers can now use consistent workflows whether they’re deploying to z/OS, cloud environments, or on-premises infrastructure. Knowledge transfers between teams instead of staying locked in silos.
The partnership leverages GitLab’s comprehensive DevSecOps platform alongside IBM’s deep mainframe expertise to create what appears to be the first truly certified solution bridging enterprise legacy systems and cloud-native development practices.
Technical Deep Dive: What’s Under the Hood
The solution addresses several technical pain points that have plagued mainframe development:
- Source Code Management Modernization: Organizations can finally retire expensive legacy library managers in favor of GitLab’s version-controlled repository system. This isn’t just about cost savings-it’s about bringing searchability, proper versioning, and collaborative features to mainframe code.
- Integrated Development Experience: Through seamless integration with IBM Developer for z/OS Enterprise Edition (IDzEE), developers get dependency-based builds, automated code scanning, and comprehensive debugging tools within their familiar environments.
- End-to-End Visibility: Perhaps most importantly, the solution provides comprehensive project management from planning to production across both mainframe and distributed environments. This unified view enables automated DevOps workflows that were previously impossible.
The Business Case: Beyond Developer Experience
While improved developer experience is valuable, the business implications run deeper. Organizations pursuing hybrid cloud strategies need applications that can span mainframe and cloud-native environments seamlessly. Traditional approaches create integration nightmares and security vulnerabilities.
The GitLab Ultimate for IBM Z solution enables incremental modernization-legacy systems continue operating while teams adopt modern practices at their own pace. This reduces the risk typically associated with mainframe modernization projects while providing a clear path forward.
From a cost perspective, replacing premium legacy tooling with modern alternatives can deliver significant savings. But the real ROI comes from accelerated delivery cycles and the ability to attract developers who expect modern development experiences.
Market Implications
This partnership signals a broader shift in how the industry thinks about mainframe modernization. Rather than treating mainframes as legacy systems to be eventually replaced, the approach recognizes them as critical infrastructure that needs to be integrated into modern development workflows.
For enterprises, this could be the catalyst needed to finally unify their development practices. The solution provides a bridge between worlds that have operated in isolation for too long.
Looking Ahead
GitLab Ultimate for IBM Z is available now, marking what could be a turning point for enterprise development practices. The success of this partnership may well determine whether other major players follow suit with similar integrated approaches.
For organizations still operating with fragmented development toolchains, the question isn’t whether to modernize-it’s whether they can afford not to in an increasingly competitive digital landscape.
The era of isolated mainframe development may finally be coming to an end. It’s about time.
##
GitLab Ultimate for IBM Z is available now. More information is available through GitLab and IBM’s partnership resources.
