VM and infrastructure specifics

2 minute read

Build machines

CloudBees CodeShip Basic

CloudBees CodeShip Basic runs Ubuntu 20.04 (Focal Fossa) on all build machines. To virtualize the build machines Linux Containers (LXC) are used. All Basic build machines run on AWS us-east-1. Basic is multi tenant meaning there are many Linux Containers running on a single AWS instance at a time.

Every build is provisioned with a new LXC instance. Changes done to the filesystem during the build are stored on a temporary filesystem in memory so your code never touches a harddrive and is completely removed as soon as the build ends.

CloudBees CodeShip Pro

All CloudBees CodeShip Pro builds run on dedicated, single tenant build machines, on individual AWS EC2 instances, in the us-east-1 region. On Pro, builds run on infrastructure equipped with version 24.0 of Docker.

The CloudBees CodeShip Pro build environment is configurable depending on plan and available in the following configurations:

  • Small: 2 CPUs, 3.75gb RAM

  • Medium: 4 CPUs, 7.5gb RAM

  • Big: 8 CPUs, 15gb RAM

  • Huge: 16 CPUs, 30gb RAM

  • Massive: 32 CPUs, 60gb RAM


All incoming ports are rejected by default except port 22, which is open to allow SSH debug sessions. Outgoing port 25 (SMTP) is closed by default so CodeShip can’t be used for spamming.

Disk space

All builds on both CloudBees CodeShip Basic and CloudBees CodeShip Pro have 10gb of disk space allocation for the build environment.

System Timeouts

On CloudBees CodeShip Basic, a build can run for up to 3 hours, although builds will time out if there is no log activity for 10 minutes.

On CloudBees CodeShip Pro, a build can run for up to 5 hours, although builds will time out if there is no log activity for 15 minutes.