Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis: change from "trusty" to "xenial" #16

Merged
merged 1 commit into from
Aug 13, 2020

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Jul 30, 2020

As the "trusty" environment is no longer officially supported by Travis, they decided in their wisdom to silently stop updating the PHP "nightly" image, which makes it next to useless as the last image apparently is from January....

This updates the Travis config to:

  • Use the xenial distro, which at this time is the default.
  • Sets the distro for low PHP versions explicitly to trusty.
  • Makes the expected OS explicit (linux).
  • The xenial distro is quite bare, so ant is not available by default. Adding this as an addon fixes that.

As the "trusty" environment is no longer officially supported by Travis, they decided in their wisdom to silently stop updating the PHP "nightly" image, which makes it next to useless as the last image apparently is from January....

This updates the Travis config to:
* Use the `xenial` distro, which at this time is the default.
* Sets the distro for low PHP versions explicitly to `trusty`.
* Makes the expected OS explicit (linux).
* The `xenial` distro is quite bare, so `ant` is not available by default. Adding this as an `addon` fixes that.
@grogy
Copy link
Member

grogy commented Aug 13, 2020

Thanks you, it looks good.

@grogy grogy merged commit c2b2c1a into php-parallel-lint:master Aug 13, 2020
@jrfnl jrfnl deleted the feature/update-travis-env branch August 13, 2020 14:40
@jrfnl jrfnl added this to the 1.0.0 milestone Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants