Hi,
We have a .travis.yml file that creates a number of jobs in the include section:
language: php
sudo: false
dist: trusty
cache:
directories:
- vendor
- $HOME/.composer/cache
before_install:
- |
if [ "x$COVERAGE" != "xyes" ]; then
mv ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/xdebug.ini{,.disabled} || true
fi
before_script:
- if [[ "$DB" == "mysql" || "$DB" == "mysqli" || "$DB" == *"mariadb"* ]]; then mysql < tests/travis/create-mysql-schema.sql; fi;
- |
if [ "x$COVERAGE" == "xyes" ] && [[ ! $(php -m | grep -si xdebug) ]]; then
echo "xdebug is required for coverage"
show original
We put the jobs in a certain order, for visual consistency (PHP version, driver, database version), but Travis does not run them in this exact order:
https://travis-ci.org/doctrine/dbal/builds/461355844
For example, you can see that some PHP 7.1 jobs have been moved in-between PHP 7.3 jobs.
Is this a bug? Or did I miss a way to enforce this order?
Thanks in advance,
Hello, there.
Indeed, we push jobs that are allowed to fail to the end of the stage, so that required jobs tend to (there is no guarantee) be executed first, so that the result is known earlier rather than later. This happens silently without any visual cues.