From support at travis-ci.com Thu Dec 7 21:23:03 2017 From: support at travis-ci.com (=?utf-8?Q?Travis=20CI=20GmbH?=) Date: Thu, 7 Dec 2017 21:23:03 +0000 Subject: =?utf-8?Q?Ubuntu=20Trusty=20update=202017=2FQ4=20and=20new=20LTS=2FLatest=20process?= Message-ID: <8ce724a4c9af4dace663cd39c.94107c8d82.20171207212246.44e9a92587.404043ff@mail59.atl31.mcdlv.net> The Travis CI build environments will be updated with following changes. View this email in your browser (http://mailchi.mp/travis-ci/ubuntu-trusty-update-2017q4-and-new-ltslatest-process?e=94107c8d82) ** Ubuntu Trusty update 2017/Q4 and new LTS/Latest process ------------------------------------------------------------ ** Schedule ------------------------------------------------------------ We're happy to announce that we will be updating our Trusty Build Images on December 11th, 2017. With this update, we will also introduce a new set of `group:` attributes for selecting build images, and the existing ones will be deprecated. ** The group: key ------------------------------------------------------------ We'll be providing the option of both a stable, long-term support image where only security updates will be made. This is the group: travis_lts option, and is enabled by default. We'll also be offering another image which will be frequently, regularly updated images with the name group: travis_latest. ** History ------------------------------------------------------------ Since the start of Travis CI, we’ve tried to provide images that could accommodate the vast majority of our users with periodic updates provided as needed. These images host a number of pre-installed software packages that are commonly requested and used. We update these as needed and requested, but there’s always been a balance to strike - do we push for cutting edge features, or do we keep to the stable and well known to work? There are plenty of benefits to both directions. Before, we’ve tried to strike a balance in a natural fashion but this led to some inconsistency in timelines for updates of images. With this new setup, we can instead offer the best of both worlds. You can read our blog post about it here: https://blog.travis-ci.com/2017-12-01-new-update-schedule-for-linux-build-images. ** Testing ------------------------------------------------------------ We are encouraging you to proactively try these new images in advance to reduce the number of surprises on Monday. This is already possible if you are using our sudo-enabled infrastructure (i.e. with sudo: required). Simply add group: edge to your .travis.yml file and you're all set. Unfortunately, this is not possible right now if you are using our container-based infrastructure (i.e. with sudo: false). ** Support ------------------------------------------------------------ If anything comes up, we'd be glad to hear from you and you can learn how to report your issues here: https://github.com/travis-ci/travis-ci/issues/8870. We're excited to see what this will bring for our users and the community. As always, please feel free to reach out to us over at support at travis-ci.com if you need our help. All the best and happy building! ============================================================ Copyright © 2017 Travis CI, All rights reserved. You are receiving this email because you signed up to receive Travis CI build environment updates. Our mailing address is: Travis CI Rigaer Straße 8 Berlin 10247 Germany Want to change how you receive these emails? You can ** update your preferences (https://travis-ci.us7.list-manage.com/profile?u=8ce724a4c9af4dace663cd39c&id=8cff25dd13&e=94107c8d82) or ** unsubscribe from this list (https://travis-ci.us7.list-manage.com/unsubscribe?u=8ce724a4c9af4dace663cd39c&id=8cff25dd13&e=94107c8d82&c=44e9a92587) . -------------- next part -------------- An HTML attachment was scrubbed... URL: