This article is about Codeship Basic.

Ubuntu Bionic

You will need roughly 2 minutes to read this article.

Ubuntu Bionic On CodeShip Basic

We are starting to run Ubuntu Bionic build containers for CodeShip Basic. In general, the overall environment is setup and configured in the same way you are familiar with. Most existing build commands should continue to work the same. The underlying OS version is just getting upgraded, specifically to Ubuntu 18.04.2 LTS (Bionic Beaver).

Rollout Plan

Starting February 18th we will start automatically opting in projects and running them on Bionic. This will be a gradual rollout, meaning we will start with a very small number of projects and steadily increase over the next several weeks. Your projects might get opted in on the first day or it could happen at a later time.

If the build is running on Bionic, step 6 of the build will say Preparing Bionic Build Container.

If you would like your projects switched to Bionic sooner, please let us know.

Key Changes

  • MySQL 5.7 running by default
  • Python 3.7 installed by default

Common Issues

Many underlying package and dependency versions changed in Bionic so it is possible you will encounter issues depending on your build configuration. If you get unexpected errors the first step is to clear your project’s dependency cache. You can also add the cs clear-cache command to the start of the build to ensure the cache is not used while you are configuring the new environment.

If the build issues persist, then take a look at your build in a debug session which allows you to look closer and experiment with other build commands. If you did any special customizations to make your projects run in the current environment, those customizations may need to either be updated for Bionic, or in some cases you may no longer need them.

Keep in mind that you have root permissions in the build environment so you are free to use tools like apt-get to further customize the environment.

Finally, if you are using any CodeShip scripts they should work on Bionic, but if you encounter any problems let us know. Also consider that with newer versions of many packages in Bionic, you may not need a particular script any longer.

Opting Out

If you have a project that is failing to build on Bionic and there is not a clear solution, you can opt that project out. Under Project Settings > General is a button to switch back to the old environment.


If the above steps do not help to get your projects running, reach out to us. We will help you work through any migration challenges. Your feedback is also helpful to us and other customers as we work on resolving issues in the new environment.

Need more help?

Contact our support team or post on Stack Overflow using the tag #codeship. Did you check the status page and changelog?

There are also several code examples and sample projects available for you to get started with.

Article not helpful?

Does this article need improvement? If so, please send feedback or submit a pull request!