Skip to content

Explicitly enable database services for Travis builds

Marek Szuba requested to merge travis_environment into version/2.2

Created by: mkszuba

Use case

From Xenial onwards services such as MySQL or PostgreSQL have to be explicitly enabled in .travis.yml. Due to issues with the availability of Perl versions we need we will stick with Trusty for the time being in spite of it being deprecated (see #112), then again it doesn't hurt to get this taken care of already.


Explicitly enable the services: mysql and postgresql in Travis builds.

Possible Drawbacks

None I can think of, enabling these services for Trusty is harmless.


Have you added/modified unit tests to test the changes?


If so, do the tests pass/fail?


Have you run the entire test suite and no regression was detected?

The change pertains specifically to Travis so running the test suite by hand doesn't help, have to wait for Travis builds on the head branch to finish.

Merge request reports