Deploy and validate Jenkins on Arm-based cloud servers
Introduction
Technology stack overview
Create an Arm-based virtual machine using Microsoft Cobalt 100
Create a firewall rule on Azure
Install Jenkins on Azure Ubuntu Arm64 virtual machine
Create a firewall rule on GCP
Create a Google Axion C4A virtual machine
Install Jenkins on GCP SUSE Arm64 virtual machine
Validate Jenkins installation
Build an Arm-native Go CI pipeline on Jenkins (GCP SUSE Arm64)
Build a Docker-based CI pipeline on Arm64
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Advanced
Reading time:  30 min
Last updated:  17 Sep 2026
Skill level:
  Advanced
Reading time:
  30 min
Last updated:
  17 Sep 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: CI-CD Microsoft Azure Cobalt Google Axion Linux Jenkins OpenJDK 17 Docker Groovy
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
CI-CD Microsoft Azure Cobalt Google Axion Linux Jenkins OpenJDK 17 Docker Groovy

Who is this for?

This Learning Path is for software developers deploying and optimizing Jenkins workloads on Arm Linux environments, specifically on Microsoft Azure Cobalt 100 processors and Google Cloud C4A virtual machines powered by Axion processors.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Provision an Azure Arm64 virtual machine (VM) using the Azure console with Ubuntu Pro 24.04 LTS.
  • Provision an Arm-based SUSE Linux VM on Google Cloud (C4A with Axion processors).
  • Install Jenkins LTS with OpenJDK 17 on an Arm64 virtual machine.
  • Validate Jenkins installation through service checks, UI access, and Arm-native pipeline execution.
  • Execute Arm-native Jenkins pipelines to verify correct runtime behavior.
  • Implement CI use cases on Arm64, including Docker-based pipelines.

Prerequisites

Before starting, you will need the following:

Summary

AI-assisted

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.

Close
?
You’ll deploy Jenkins on Arm-based cloud servers and validate an Arm-native CI/CD setup. First, you’ll provision an Azure Cobalt 100 VM, open port 8080, install Jenkins LTS with OpenJDK 17, and verify the aarch64 runtime. Then, you’ll run Arm-native pipelines, including Docker-based jobs, and configure a Google Cloud firewall rule for Axion C4A access.

Frequently asked questions

AI-assisted

These FAQs were 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.

Close
?
Which Azure VM series should I choose for a Cobalt 100 deployment?
Use the Dpsv6 size series.
How do I know that Jenkins installed correctly on the Azure VM?
Jenkins runs as a system service and is accessible on port 8080. If the installation is successful, you’ll be able to load the Jenkins UI and confirm that it uses Java 17 on an Arm64 (aarch64) host.
What should I check if I can’t reach the Jenkins UI on port 8080?
Verify that the Jenkins service is running and that an inbound TCP rule for port 8080 exists in the Azure network security group attached to the VM’s network interface or subnet. Also confirm that you’re using the correct public IP and port.
Where do I configure the cloud network access for Jenkins?
Create the Azure network security group inbound TCP rule for port 8080 in the Azure portal. For an Axion C4A instance on Google Cloud, create the inbound firewall rule in the Google Cloud Console.
How do I confirm that the environment is Arm-native before running pipelines or Docker-based jobs?
Check that the system reports Arm64 (aarch64) and that Jenkins runs with OpenJDK 17. Ensure that port 8080 is open so that the controller is reachable before you start pipelines.
Next