Build a CI/CD pipeline with GitLab on Google Axion
Introduction
Create a Google Axion-based GitLab self-hosted runner
Automate multi-architecture builds and deployments with GitLab CI/CD
Next Steps
Build a CI/CD pipeline with GitLab on Google Axion
Who is this for?
This is an advanced topic for DevOps professionals who are looking to build a CI/CD pipeline with GitLab on Google Axion based self-hosted GitLab runners.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Create a Google Axion based GitLab self-hosted runner
- Build a CI/CD pipeline with multi-architecture support
- Build multi-architecture docker images using native GitLab runners on x86 and Arm
- Automate the build and deployment of a multi-arch application with GitLab CI/CD
Prerequisites
Before starting, you'll need the following prerequisites:
- A Google Cloud account . Create an account if needed.
- A computer with Google Cloud CLI and kubectl installed.
- A valid GitLab account
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll create a Google Axion-based self-hosted GitLab Runner and wire it into a GitLab CI/CD pipeline that produces a multi-architecture container image. First, you’ll register the runner, choose an executor that fits your environment, and confirm it is available to your project. Then, you’ll configure the pipeline to build architecture-specific images on native runners for Arm and x86, push them to a container registry, and assemble a single multi-architecture image using the
docker manifest approach. You’ll then trigger a pipeline, see jobs land on the intended runners, and verify that the published image advertises both arm64 and amd64 in its manifest.