Skip to content

Travis: reactivate warnings about different API and schema versions

Marek Szuba requested to merge feature/travis_version_checks into master

Created by: mkszuba


On Travis, make sure the home-directory file instructing the Registry to globally disable version checks is absent before launching the test suite.

Use case

Since the Operations meeting on 2019-08-27 the bumping of Ensembl API and DB-schema version numbers has been an Ensembl-wide policy. Therefore, have Travis take notice of possible discrepancies in this respect.


Version mismatches will be easier to spot.

Possible Drawbacks

If Core version bumps happen before other teams have published theirs, there will be a (hopefully short) time window of expected mismatches.


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?

No, the change in question only affects Travis builds. On which note, with the test DBs on master not having been fully patched to 99 yet the expected outcome of this change is for Travis to fail.

Merge request reports