The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Runner SaaS is the product development effort for Runners on GitLab SaaS.
Our vision for GitLab Runner SaaS is to provide developers with a zero-friction, secure, highly performant, and reliable CI/CD build experience for the market-leading operating systems and development technologies.
Check out our Ops Section Direction "Who's is it for?" for an in depth look at the our target personas across Ops. For Runner, our "What's Next & Why" are targeting the following personas, as ranked by priority for support:
|Offer Name||Offer Status|
|GitLab SaaS Runners on Linux||GA|
|GitLab SaaS Runners on Windows||Beta|
|GitLab SaaS Runners on macOS x86-64||Beta|
The table below represents the current strategic priorities for Runner SaaS. This list will change with each monthly revision of this direction page.
|Theme-Category||Item||Why?||Target delivery QTR|
|SaaS Runners on Linux||Experiment - offer GCP n1-standard-2 VM's on GitLab SaaS Linux Runners; Experiment - offer GCP n1-standard-4 VM's on GitLab SaaS Linux Runners||The ongoing feedback from customers and users is that the current build machine type offered on the SaaS Runners on Linux is not powerful enough to run specific workflows efficiently. In one example, a similar CI job on a competing hosted solution ran in 12 minutes compared to 28 minutes on the GitLab SaaS Runners. To accelerate offering more compute machine types on GitLab SaaS, the initial MVC will experiment with providing two additional types of build machine types on the GitLab SaaS Runners for Linux. This effort will inform the work planned in Q4 to extend the various compute offerings available on the SaaS Runners on Linux.||Q2 FY 2023|
|SaaS Runners on macOS||GitLab SaaS Runners on macOS X86-64 Limited Availability||In Q3 FY 2022, we launched the Runner SaaS for macOS beta. The user and customer demand for this service have been exceptional. Further reinforcing the one DevOps strategy, the current beta participants strongly favor having a fully integrated build solution for the Apple ecosystem embedded in GitLab. We plan to launch this offer in limited availability in Q2 FY 2023 and follow that with a general availability launch in the second half of FY 2023.||Q3 FY 2023|
|SaaS Runners on macOS||GitLab SaaS Runners on macOS Apple Silicon M1 Beta||The current GitLab SaaS Runners on macOS beta offer provides a build environment for the Apple ecosystem on x86-64 compute. The next iteration of the GitLab SaaS Runners on macOS will include providing Runners on Apple Silicon, starting with the Apple M1 processors.||Q3 FY 2023|
|Scalability||Implement a new autoscaling solution - GitLab Runner SaaS for Linux OS||The GitLab Runner SaaS for Linux with docker container builds executes millions of CI jobs each month. The autoscaling architecture that is the foundation of this solution has served us well. However, since its introduction, we have launched new autoscaling solutions to manage the Runner SaaS for Windows and macOS. In addition, the core technology used for Linux, Docker Machine, is no longer maintained by Docker. Though we maintain a fork of Docker Machine, the right long-term strategy is to iterate towards the Next Runner autos-scaling architecture for the Runner SaaS. This architectural technology pivot will enable us to accomplish several goals. First - enabling GitLab to scale over the next five years. Second, as a critical foundational enabler to consistently achieve and exceed our CI Runners SLO goal of 99.95%. Finally, the autoscaling technology that we implement to manage the scale of GitLab SaaS is the same technology made available to customers that self-manage Runner Fleets.||Q3 FY 2023|
|SaaS Runners on Windows||Runner SaaS for Windows General Availability||We launched the Runner SaaS for Windows in beta in FY21Q1. At the time, our initial plan was to transition the offer to GA within a few quarters. However, due to other strategic priorities, we delayed that timeline. Now users and customers rely on a Windows build solution hosted on GitLab SaaS for their mission-critical CI/CD builds, so we must migrate the Windows offer to GA.||Q3 FY 2023|
|SaaS Runners on Linux||Offer multiple compute options on GitLab SaaS||There has been increasing demand to offer more compute offerings on GitLab SaaS Runners from customer feedback in the past few months. For some customers, higher compute GitLab SaaS Runners is a must-have for migrating more CI/CD workloads to GitLab SaaS. The launch of this offer will have a net positive impact on the Verify stage monthly active users. However, there are foundational elements that we need to implement on GitLab SaaS to provide the user and customer community a first-class experience.||Q4 FY 2023|
|SaaS Runners on macOS||GitLab SaaS Runners on macOS X86-64 General Availability||As part of our single DevOps platform strategy, we must offer customers the ability to build applications targeted for multiple platforms in one pipeline without configuring or managing a build environment. This means offering an on-demand and scalable macOS build environment with the same service levels as our Linux SaaS Runners. Following the limited availability launch, our team will be working with our cloud infrastructure provider to enhance the scalability of the computing stack to support the projected CI workload demands at general availability.||Q4 FY 2023|
In addition to prioritizing the work required to deliver the strategic priorities listed above, the Runner SaaS team must prioritize and allocate resources for maintenance, security fixes, bugs, and feature enhancements in each milestone. A substantial percentage of the investment allocation for the maintenance bucket will be allocated across the following sub-categories:
Organizations that use Cloud-native CI/CD solutions, such as GitLab.com, CircleCI, and GitHub, can run their CI/CD pipelines and get to a first green build without setting up build servers, installing and configuring build agents, or runners.
In addition to eliminating CI build server maintenance costs, there are other critical considerations for organizations that can migrate 100% of their CI/CD processes to a cloud-native solution. These include security, reliability, performance, multiple build server and configuration options, and on-demand scale.
Some competitors currently focus on building platform speed and performance as a critical competitive differentiator. Today on GitLab SaaS, we execute docker container CI builds only on GCP 1vCPU n1-standard-1 instances. From our perspective, GitLab Runner SaaS is well-positioned to compete on the performance and speed vector over the long term. First, the Runner core build execution engine is highly performant. Secondly, we are introducing next-gen autoscaling technology that will benefit even faster time to job execution start. Finally, as we release more compute offerings on GitLab SaaS, users will benefit from speedier build times for compute-intensive workloads.
Apple released Xcode Cloud GA Apple WWDC22, and the ~34 million Apple developers worldwide now have an Apple product option for building, testing, and deploying mobile applications integrated into the Xcode development environment.
Xcode Cloud aims to make it very easy for Apple app developers to adopt CI/CD as you use Xcode to set up and configure CI/CD workflows. By default, Xcode analyzes a project configured to use Xcode Cloud, and automatically suggests a default workflow. The default workflow includes build, analyze, test and archive. In future updates, we will add a more detailed analysis.
With this initial release, Apple appears to signal that the vision and future is frictionless CI/CD for Apple developers. Xcode Cloud requires the use of a supported git repository. So given the out of the box support for GitLab SaaS and GitLab Self-Managed, this new offer could prove appealing to startups or smaller teams focused on development for the Apple ecosystem.
For GitLab customers that are building applications for multiple platforms, GitLab SaaS continues to be the right choice as the single DevOps platform. In one pipeline hosted on GitLab SaaS, a customer can execute build jobs targeting Android, Apple iOS and Windows.
One of the goals of the GitLab Mobile App strategy is to provide frictionless CI/CD for all mobile application development (iOS, Android). Therefore our value proposition remains strong, even in light of the new Xcode Cloud offer.
|1 vCPU, 4GB RAM class build VM||Available||Not available||Available|
|2 vCPU, 8GB RAM class build VM||Not available||Available||Available|
|4 vCPU, 16GB RAM class build VM||Not available||Not available||Available|
|8 vCPU, 32GB RAM class build VM||Not available||Not available||Available|
|16 vCPU, 32GB RAM class build VM||Not available||Not available||Available|
|2 vCPU, 8GB RAM class build VM||Available||Not available|
|3 vCPU, 16GB RAM class build VM||Not available||Available|
|….||GitHub||Apple - Xcode Cloud GA||CircleCI||Bitrise.io|
|Positioning Statement||A GitHub-hosted runner is VM hosted by GitHub with the GitHub actions runner application installed.||A CI/CD service built into Xcode, designed expressly for Apple developers.||Industry-leading speed. No other CI/CD platform takes performance as seriously as we do.||Build better mobile applications, faster|
|Value Proposition||When you use a GitHub-hosted runner, machine maintenance and upgrades are taken care of.||Build your apps in the cloud and eliminate dedicated build infrastructure.||The macOS execution environment allows you to test, build, and deploy macOS and iOS apps on CircleCI.||CI for mobile - save time spent on testing, onboarding, and maintenance with automated workflows and triggers|
|macOS Virtual Machine Specs||3-core CPU, 14 GB RAM||TBD||Medium: 4 vCPU, 8 GB RAM; Large: 8 vCPU, 16 GB RAM; Metal 12 vCPU 32 GB RAM||Standard: 4 vCPU, 19 GB RAM; Elite 8 vCPU 35 GB ram; Elite XL 12 vCPU 54 GB RAM|
If you have questions about a specific runner feature request or have a requirement that's not yet in our backlog, you can provide feedback or open an issue in the GitLab Runner repository.
This direction page was revised on: 2022-06-23