Ubuntu 18.04.1 LTS (Bionic Beaver)

Transferred from https://github.com/travis-ci/travis-ci/issues/5821.

Bionic 18.04 was released in April 2018.

Please add Bionic to Travis CI.

It’s good Xenial 16.04 was recently added (https://blog.travis-ci.com/2018-11-08-xenial-release). :+1:

However, Trusty 14.04 will be EOL soon in April 2019 so it’ll be good to have the both supported Ubuntu releases available.

https://linuxlifecycle.com

(Python 3.7 not added for bionic images is for Python 3.7 on Bionic, but this is more general issue.)

28 Likes

What is the status of supporting Ubuntu 18.04.1 LTS (Bionic Beaver) in travis CI?

Anyone could update on this?

3 Likes

Transferred from https://github.com/travis-ci/travis-ci/issues/582

The correct link is: https://github.com/travis-ci/travis-ci/issues/5821

Actually, this was previously tracked as https://github.com/travis-ci/travis-ci/issues/9460 but later merged into 5821.

Thanks, I’ve fixed the link.

The issue is closed now and says that Bionic will be added “in the near future”. Is there a more concrete timeline for this?

1 Like

Are there any updates regarding this?

2 Likes

Any eta or update?

2 Likes

Expect to see bionic support shortly after the release of Ubuntu 22.04.

3 Likes

Any updates on this?

The slow sounds of a dying product.

1 Like

Any updates?

2 Likes

Upvote this

3 Likes

Technically speaking, they can buy themselves some time if they purchase the Extended Security Maintenance from Canonical. I hope they confirm this somewhere…

A potential issue of supporting 18.04 is that RethinkDB doesn’t officially support 18.04 yet.

Issue about it


Pre-release which supports Bionic

Not sure if that should be a blocker, given RethinkDB company shutting down https://rethinkdb.com/blog/rethinkdb-shutdown/ , and no new community releases since mid-2017. Anyone needing it can continue to use Xenial.

It would be great if Travis CI Dot Com defined what is the minimal acceptance criteria for letting a new Ubuntu version be used as part of early release , so that community members can understand the blockers, and help clear them.

1 Like

I would love to see this happen, so that we can get a more up to date g++ / libtsan ; the sanitizers for older gcc seems to be buggy and produce false positives.

I’m using a very recent Fedora in a container and the sets of tsan errors I’m getting are completely different, and I trust those more as they use gcc-9.

I see several threads where people are already using bionic

https://travis-ci.org/kivy/kivy/jobs/548014558 seems to be reporting that it is a Bionic image

https://github.com/travis-ci/travis-build/search?q=bionic&unscoped_q=bionic has a few results.

It’s trying to use Bionic, but the image isn’t available:

3.5 is not installed; attempting download

Downloading archive: https://storage.googleapis.com/travis-ci-language-archives/python/binaries/ubuntu/18.04/x86_64/python-3.5.tar.bz2

0.06s$ curl -sSf -o python-3.5.tar.bz2 ${archive_url}

curl: (22) The requested URL returned error: 404

Unable to download 3.5 archive. The archive may not exist. Please consider a different version.

If you need 3.5, you need to stay on Trusty.

That sounds like Bionic is now available for 2.7 and 3.6+, and indeed it is!

image

image

https://travis-ci.org/hugovk/test/builds/548201815

Thanks!

Will it be available for pypy and pypy3?