The Xenial Build Environment
- What This Guide Covers
- Using Xenial
- Differences from the Trusty images
- Environment common to all Xenial images
- Ruby support
- Python support
- Go support
- JVM (Clojure, Groovy, Java, Scala) support
- Perl support
- PHP support
- Databases and services
- Other Ubuntu Linux Build Environments
What This Guide Covers #
This guide provides an overview of the packages, tools and settings available in the Xenial environment.
Using Xenial #
To route your builds to Ubuntu Xenial 16.04, add the following to your
Please note that Xenial is available on our hosted fully virtualized infrastructure. If you are running an Enterprise installation, please reach out to email@example.com to see how you can use the Xenial Docker images.
Differences from the Trusty images #
Xenial includes the following changes and improvements:
Third party apt-repositories removed #
While third party apt-repositories are used during the Xenial image provisioning, they are all removed from the Xenial build image. This has two benefits; a) reduced risk of unrelated interference and b) faster apt-get updates.
To specify a third party apt-repository, you can add the source with the apt addon and specify the packages. For example:
dist: xenial addons: apt: sources: - ppa:chris-lea/redis-server packages: - redis-tools - redis-server
If you depend on these repositories in your build, you can use the following
source line to get them back:
Services disabled by default #
On our Xenial infrastructure, to speed up boot time and improve performance we’ve disabled all services, including the ones that are started by default on Trusty.
Add any services that you want to start by default to your
services: - mysql - redis
Environment common to all Xenial images #
The following versions of Docker, version control software and compilers are present on all builds, along with more language specific software described in more detail in each language section.
All preinstalled software not provided by distro is installed from an official release –
either a prebuilt binary if available, or a source release built with default options.
For preinstalled language interpreters, a standard version manager like
rvm is used if available for the language.
Version control #
Compilers and Build toolchain #
- clang and llvm 7
- cmake 3.12.4
- gcc 5.4.0
- ccache 3.2.4
- shellcheck 0.6.0
- shfmt 2.6.3
- Docker 18.06.0-ce is installed
- docker-compose 1.23.1.
Ruby support #
- Pre-installed Rubies:
- The default ruby is
- Other ruby versions can be installed during build time.
Python support #
- Supported Python versions:
- Pre-installed Python versions:
3.6.7will be used when no language version is explicitly set.
If you’re getting errors about PyPy
pypy is not installed; attempting download, use one of the more recent python versions such as
- For builds specifying
nvmis automatically updated to the latest version at build time. For other builds, the stable version at image build time has been selected, which is 0.33.11.
- The following NodeJS versions are preinstalled:
Go support #
Other Go versions can be installed during build time by specifying the language versions with the
JVM (Clojure, Groovy, Java, Scala) support #
openjdk11on x86, default is
Other JDKs, including Oracle’s, can be acquired if available by specifying
The following table summarizes the Pre-installed JVM tooling versions:
Perl support #
- Default version on Xenial is
- Supported versions
5.30can be installed by using the
PHP support #
- For dynamic runtime selection,
- The following PHP versions are preinstalled:
Databases and services #
The following services and databases are preinstalled but but do not run by default.
To use one in your build, add it to the services key in your
|postgresql||9.4 9.5 9.6 10|
Other Ubuntu Linux Build Environments #
You can have a look at the Ubuntu Linux overview page for the different Ubuntu Linux build environments you can use.