AOSC Wiki / Developer / Infrastructure / .


Buildbots that can be used by AOSC developers

General Information§

This page contains information about AOSC Buildbots.

AOSC buildbots are all connected to our central relay nodes ( and some others), and are allocated fixed port numbers. To be specific, ports are allocated as per the buildbot's architecture:

  • AMD64: 22001 - 23000
  • MIPS: 23001-24000
  • ARM: 24001-25000
  • PowerPC: 25001-26000
  • RISC-V: 26001-27000
  • LoongArch: 27001-28000
  • Emulation hosts: 28001-29000

Before You Start§

  1. You are not to use these community Buildbots for personal purposes, nor to resell them.
  2. Do not alter terminal sessions or files in others' workspaces.
  3. You must inform contributors and infrastructure administrators regarding any changes to the host system, network configuration, or hardware.

Signing In§

Submit your public keys for authentication at the dev-pubkeys repository, then view Buildbots on GitHub for connection infomation.

For most buildbots, scratch disk is at /buildroots, create your own Ciel workspace there, and don't forget to clean it up after finishing your work, storage space isn't infinite unfortunately.

Contributing a Buildbot§

If you would like contribute your device to AOSC, please make sure your device has a usable Ciel 3 installation, and contact Kexy Biscuit [email protected] by Telegram (preferred) or email, providing:

  • Name for your device;
  • Port number of your choice, correspondent to the device's architecture;
  • Shell access for Kexy Biscuit for Relay configuration.

List of Buildbots§

Information Circle
  • port_number - 10000 is occupied by that machine. See information above.
  • The parameter "Speed" presents an approximation on the relative performance of each Buildbot. To benchmark, download and run the buildbot-benchmark.bash script.
  • A Port with a strikethrough means that the buildbot is not online recently.

AMD64 (22001 - 23000)§

Yerus22333AMD EPYC 7H12 @ 2.6 - 3.3GHz1TiB173sJiangjin Wang

MIPS (23001-24000)§

Resonance23541Loongson 3B-4000 (R4) @ 1.80GHz (LX-2510)32GiB3748sKexy BiscuitCommunity crowdsourced; direct access with ssh -4p23541 [email protected]; repo mirror at http://localhost/debs/, BuildKit mirror at http://localhost/aosc-os/os-amd64/buildkit/
JellyShrimp23869Loongson 3A-4000 (R4) @ 1.80GHz (A1901)16GiB5604sMingcong Bai

ARM (24001-25000)§

kp920244262 * 48-Core Huawei Kunpeng 920 @ 2.60GHz (Huawei Taishan 2280 v2; 94 cores allocated)192GiB (145GiB allocated)439sUndisclosedDirect access with ssh -4p2223 [email protected]
eleventh248088-Core Huawei Kunpeng 920 @ 2.40GHz16GiB1582sUndisclosedDirect access with ssh [email protected]:20022 [email protected]

PowerPC (25001-26000)§

PowerNV25202IBM POWER9 CPU (4 cores, 16 threads)128GiB1293sMingcong Bai

RISC-V (26001-27000)§

GreenGoo26666T-Head XuanTie C920 @ 2GHz96GiB1376sIcenowy ZhengTBC

LoongArch (27001-28000)§

Stomatopoda2786316x LA464 cores @ 2.20GHz (Loongson 3C5000)32GiB1376s (with LLVM 16.0.4)Loongson Technology (Wuhan)Direct access with ssh -p2222 [email protected]

Emulation Hosts (28001-29000)§

Taple28002AMD Ryzen R5 5500 @ 3.9 - 4.4GHz32GiB726sLain YangLocal mirror at http://localhost/debs
PorterAlePro28003AMD Ryzen 9 3950X @ 3.50 - 4.70GHz64GiB313sMingcong Bai

List of archived buildbots§

Please note that the following is not an exhaustive list.

Maple24191Snapdragon 8cx Gen 3 (8) (4 * Cortex-X1 @ 3.00GHz + 4 * Cortex-A78 @ 2.40GHz)16GiB1098sCanarypwn
Zinfandel242224 * Firestorm @ 3.2GHz + 4 * Icestorm @ 2.06GHz (Apple M1 chip)16GiB-Salted FishLocal mirror:
Mio242424 * Firestorm @ 3.2GHz + 4 * Icestorm @ 2.06GHz (Apple M1 chip)16GiB-Mag MellDirect access with ssh -p8765 [email protected]; local mirror:
JellyXavier244444 x dual core NVIDIA Carmel CPU clusters @ 2.26GHz (NVIDIA Jetson AGX Xavier Developer Kit)16GiB-Mingcong Bai
JellyPhy244518-Core Phytium D2000 @ 2.30GHz32GiB2589sMingcong Bai
KirinPENDINGHUAWEI Kirin 9006C (8) (1 * Cortex-A77 @ 3.13GHz + 3 * Cortex-A77 @ 2.54GHz + 4x [email protected])8GiB1826sRick LiuDirect access with ssh -p8038 [email protected]
SiFarce26002SiFive FU740 @ 1.4GHz (SiFive HiFive Unmatched)16GiB-Mingcong Bai
marianne26055SiFive FU740 @ 988MHz (SiFive HiFive Unmatched)16GiB22515sIcenowy ZhengScratch needs to be mounted manually by in /root (currently using the scratch disk from lorenz); behind GFW, a HTTP proxy is available at http://dedue:8118, device sponsored by the PLCT Lab
leonie26056SiFive FU740 @ 988MHz (SiFive HiFive Unmatched)16GiB22612sIcenowy ZhengScratch is on NVMe disk ,maybe buggy, investigation needed; behind GFW, a HTTP proxy is available at http://dedue:8118, device sponsored by the PLCT Lab
Yukoaioi27001Quad core @ 2.50GHz (Loongson 3A5000)16GiB-Mag MellDirect access with ssh -p9876 [email protected]
PorterAle28001Intel i7-8700T @ 2.40 - 4.00GHz16GiB996sMingcongBai

Maintainer Notes§


Between the relay and the buildbots, Popub is used to forward your SSH port to our relay server. For usage of Popub, please read their README.

Each buildbot is allocated 2 ports; the smaller one is for connection between your machine and the relay, and the larger one is for outside connections to the relay. For example, the AMD64 buildbot Yerus is using 12333 and 22333, where Yerus forwards its SSH port using popub-local to 12333 on the relay, and the relay exposes this port to the outside on port 22333.