Jenkins-CI/CD-Hardwareanforderungen: RAM, CPU, Speicher & Build-Agenten
Planen Sie Jenkins-CI/CD-Hardware für RAM, Controller-Speicher, Build-Agenten, Java, Job-Konkurrenz und praktische Empfehlungen für die Bereitstellung von ZimaOS.
Jenkins CI/CD hardware requirements at a glance
Size Jenkins CI/CD from verified upstream requirements first, then add headroom for the real workload and persistent data.
- RAM
- Official minimum: 256 MB; small-team recommendation: 4 GB+
- CPU
- No universal controller-core minimum published
- Storage
- 1 GB minimum; 10 GB Docker recommended minimum; 50 GB+ small team
- Java
- Current 2026 LTS supports Java 21 or 25
- Key workload
- Controller orchestration is separate from build execution
- Best Zima starting point
- ZimaBoard 2 832 for a small controller
From official requirements to the right setup
Separate Jenkins controller sizing from build-agent sizing. The controller manages HTTP, jobs, plugins, and JENKINS_HOME; agents perform builds and tests.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Number of jobs
- Concurrent builds
- Controller executors
- Agent count
- Build memory
- Build CPU
- JENKINS_HOME growth
- Artifact retention
Official minimum requirements
Jenkins publishes numerical memory and disk minimums plus small-team recommendations; controller CPU and agent hardware remain workload-dependent.
The 256 MB RAM and 1 GB disk figures are bare minimums, not a good modern CI target. Docker and small-team guidance is higher.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 256 MB | Small-team recommendation is 4 GB+. | |
| 1 GB | 10 GB is recommended as a Docker minimum. | |
| 50 GB+ | Room for JENKINS_HOME, plugins, history, artifacts. | |
| No universal numerical minimum published | Depends on users, jobs, plugins, nodes. | |
| Java 21 or Java 25 | Current 2026 LTS support. | |
| 0 | Delegate builds to agents. | |
| Not required for Jenkins itself | Agents may need GPU for specific jobs. |
When to upgrade your hardware
More concurrent builds
Controller memory pressure
JENKINS_HOME growth
Plan hardware growth with confidence
Fast JENKINS_HOME storage
Use reliable SSD storage for controller state.
SSD or NVMeController RAM
Add memory as users, plugins, and connections increase.
Higher-RAM hostArtifact capacity
Expand persistent storage or externalize artifacts.
Larger SSD/HDD poolDedicated build agents
Scale CPU/RAM according to build type and concurrency.
Separate build nodes or stronger computeCan it run on ZimaOS?
Install Jenkins CI/CD from the ZimaOS App Store
A specific public Jenkins CI/CD page is verified.
Open Jenkins CI/CD in the ZimaOS App Store ↗Follow Jenkins Docker guidance
Persist JENKINS_HOME and separate controller from heavy builds.
Open Jenkins Docker installation docs ↗Use agents for builds
Jenkins recommends controller executors set to 0.
Open Jenkins hardware recommendations ↗Zima hardware for Jenkins CI/CD
A small Jenkins controller fits on ZimaBoard 2, but local build execution can become CPU-, RAM-, and storage-heavy quickly.
Choose by workload
Controller workload is modest when builds run elsewhere.
Build-agent CPU/RAM and artifact storage dominate.
Zima product guidance is a practical workload mapping, not an upstream hardware certification.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and a 4-core N150 limit heavier CI, databases, and high-concurrency work | Get Now |
| ZimaBoard 2 1664 | More containers and memory-heavier services on a low-power CPU | Moderate multi-app workloads |
|
CPU throughput is unchanged from the 832 model | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, and database-heavy workloads | Builds, indexing, many connections, or demanding containers |
|
16 GB RAM can still limit very large builds, databases, or local AI | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
How much RAM does Jenkins need?
Jenkins publishes 256 MB as a minimum and 4 GB+ as a recommended small-team configuration.
How much disk space does Jenkins need?
The minimum is 1 GB; Jenkins recommends at least 10 GB for Docker and 50 GB+ for a small team.
How many CPU cores does Jenkins need?
Jenkins does not publish one universal controller-core minimum.
Which Java version does current Jenkins need?
For the current 2026 LTS line, Jenkins supports Java 21 or Java 25.
Should Jenkins builds run on the controller?
Jenkins recommends setting controller executors to 0 and delegating builds to agents.
Can ZimaBoard 2 832 run Jenkins?
Yes as a practical small controller, especially when builds run on agents.
Does Jenkins need a GPU?
Not for Jenkins itself; an agent may need GPU for specific jobs.
When should I choose ZimaCube 2 Pro?
For heavier local CI, higher concurrency, larger artifact storage, or broader consolidation.
