By Mike Gilfix 3 min read
January 14, 2021

IBM is expanding its strategic partnership with GitLab to help companies automate work across business users, developers and IT teams. 

IBM is on a mission to help clients automate the enterprise to unlock productivity, speed and cost savings. We already offer automation capabilities that combine AI and machine learning with process mining, robotic process automation (RPA), automated decisions, workflow and document management.  

With GitLab Ultimate for IBM Cloud Paks, a new offering sold by IBM and backed by GitLab and IBM, clients can streamline collaboration to improve productivity and accelerate innovation. In partnership with GitLab, we are integrating GitLab with IBM Cloud Paks and bringing IBM Watson AIOps and DevOps together to make teams more agile and efficient, enhancing IBM DevOps capabilities.

IBM Cloud Paks + GitLab

IBM DevOps along with Gitlab will provide our customers with the ability to bring automation to the software delivery process for IBM Cloud Paks:

A new GitLab connector in IBM Cloud Pak for Integration enables GitLab to interact with 100s of popular applications to automate IT processes. For instance, a release request approval in ServiceNow can automatically trigger deployment in GitLab.

IBM Watson AIOps + GitLab

The IBM Watson AIOps and GitLab integration will automate of the work of site reliability engineers (SREs) by ingesting data and events from GitLab across the software development lifecycle, including code pushes, commits, reviews, tests, deployments and releases. 

Combining this data with operational datasets and applying artificial intelligence (AI) models, IBM Watson AIOps can identify and eliminate risks, reduce incident counts and improve incident response. For example, when responding to an incident, an SRE will be able to quickly identify which services changed, how well they were tested and which developers updated the highest-risk portions of the code base so that they can rapidly find the right people to involve in problem determination and incident response.

IBM DevOps + GitLab

As clients embark on delivering an idea to the market, they are inundated with choices on DevOps tooling and faced with some common questions:

  • Can I plan and deliver my software product securely and efficiently without any bugs?
  • Can the different teams collaborate with each other efficiently without running into tool boundaries?
  • Am I able to manage my releases and deploy onto multi-architecture platforms?

Answering these questions has often led to a multitude of disjointed tools that clients have to integrate across their toolchain. 

With GitLab Ultimate for IBM Cloud Paks and IBM DevOps, clients can utilize an integrated experience out of the box across the DevOps lifecycle (plan, code, build, test, code, release, deploy, operate and monitor) to deliver applications securely, collaboratively, efficiently and with agility.

System Z + GitLab

GitLab integrates with IBM Linux on Z and RedHat OpenShift to help application developers deploy to more resilient systems. With support for GitLab runner on Z, mainframe clients can embrace modern tooling for their DevOps journey and bring ideas to market faster.

Our clients have diverse toolchains to support the diverse range of use cases, challenges, and goals among them. By partnering with GitLab, we’re helping our clients unify their DevOps and automation experiences as clients automate the enterprise. 

Learn more

Categories

Automation  |  Cloud  |  devops  | 
Mike Gilfix
Chief Product Officer, IBM Cloud Paks

More from Automation
September 29, 2023

Real-time transaction data analysis with IBM Event Automation

3 min read - As the pace and volume of digital business continue to increase, organizations are facing mounting pressure to accelerate the speed at which they do business. The ability to quickly respond to shifting customer and market dynamics has become key for contending with today’s growing digital economy. In a survey run by IDC, a leading provider of global IT research and advice, 43% of technology leaders indicated that they were “planning to deliver innovative digital products and services at a faster…

September 28, 2023

In observability, “automation” is spelled I-N-S-T-A-N-A

3 min read - Modern application environments need real-time automated observability to have visibility and insights into what is going on. Because of the highly dynamic nature of microservices and the numerous interdependencies among application components, having an automated approach to observability is essential. That’s why traditional solutions like New Relic struggle to keep up with monitoring in cloud-native environments.  Automation in observability is a requirement When an application is not performing properly, customers are unhappy and your business can suffer. If your observability…

September 27, 2023

Debunking observability myths – Part 6: Observability is about one part of your stack

3 min read - In our blog series, we’ve debunked the following observability myths so far: Part 1: You can skip monitoring and rely solely on logs Part 2: Observability is built exclusively for SREs Part 3: Observability is only relevant and beneficial for large-scale systems or complex architectures Part 4: Observability is always expensive Part 5: You can create an observable system without observability-driven automation Today, we're delving into another misconception about observability—the belief that it's solely applicable to a specific part of your stack or…

September 19, 2023

Observing Camunda environments with IBM Instana Business Monitoring

3 min read - Organizations today struggle to detect, identify and act on business operations incidents. The gap between business and IT continues to grow, leaving orgs unable to link IT outages to business impact.  Site reliability engineers (SREs) want to understand business impact to better prioritize their work but don’t have a way of monitoring business KPIs. They struggle to link IT outages to business impacts because data is often siloed and knowledge is tribal. It forces teams into a highly reactive mode…