Ubuntu 14.04 LTS – Trusty Tahr

Codeship News

Reading Time: 2 minutes

We are pleased to announce that our build infrastructure has been upgraded to Ubuntu Trusty. This means that your builds will run in an updated and more stable environment. We worked hard during the past couple of months to make this upgrade as smooth as possible.

Give Ubuntu Trusty a try

There is a special branch codeship-trusty to test your Ubuntu Trusty compatibility. If you push to that branch we will run your build in the new Ubuntu Trusty environment. This is a safe way to check if your projects are compatible with Ubuntu Trusty.

Switch to the new Ubuntu Trusty environment

After making sure your project runs fine under Ubuntu Trusty you can go to the project settings and change the architecture to Ubuntu 14.04. This means that from now on all builds will run in the new updated and more stable Ubuntu Trusty environment. No worries, you can still change it back to Ubuntu 12.10.

Change your project architecture in your project's general settings

Your next steps

  • test your Codeship project on the codeship-trusty branch
  • set the project architecture to Ubuntu 14.04
  • be happy

Sign up for a free Codeship Account

End of Life (EOL) for Ubuntu 12.10 (Quantal Quetzal)

Everything has an end. Thanks little quetzal for serving the last 1,5 years. We will fade out our Ubuntu Quantal build environment by the end of october.

  • New projects will be on Ubuntu Trusty by default by the end of August.
  • We will upgrade all projects to Ubuntu Trusty by the end of October.

Please make sure to upgrade your projects as soon as possible to ensure that you have enough time to test your projects under Ubuntu Trusty.

In case something unexpected happens in our new trusty environment please don’t hesitate to contact us at support@codeship.io

Subscribe via Email

Over 60,000 people from companies like Netflix, Apple, Spotify and O'Reilly are reading our articles.
Subscribe to receive a weekly newsletter with articles around Continuous Integration, Docker, and software development best practices.



We promise that we won't spam you. You can unsubscribe any time.

Join the Discussion

Leave us some comments on what you think about this topic or if you like to add something.

  • Luke

    Just curious, but wouldn’t be much simpler for you to spin up a Docker container to run the tests and builds command? Where you specify, for example, the node version and so on?
    So you could completely abstract your running infrastructure to the building/testing process

    • beanieboi

      Hey Luke,

      thats basically what we do. We use pure LXC containers instead of Docker. But nevertheless you need a base system which runs inside the container, which provides needed libraries in specific versions etc. Not all tests suites can run in isolation, you need databases, 3rd party libraries, 3rd party tools etc.
      These tool were provided by the base system. Our base system was Ubuntu Quantal which is quiet old now. We upgraded the base system, which means that libraries and tools are available in newer versions. For most of our customers nothing will change, they specific the ruby/node version they need and run their tests. But that applies only to a few customers!

      thanks for your input! i hope i could clarify the upgrade

      happy shipping,
      best

      ben

      • Luke

        Super clear :) thanx Benjamin for the clarification.

      • Nick

        Is meaningful for us as 14.04 ships with a newer different version of glibc, which could produce compiled that doesn’t execute on anything thats not running at least that version of glibc..

        • beanieboi

          Which glibc are you running in production?