travis: Fix the order of running the test suites in Travis CI.

This commit fixes the order in which we run the test suites in Travis
CI. Most of the PRs include changes only to backend/frontend and it is
fairly rare for them to break production test suite. Since travis runs
atmost four jobs at a time, most of the time developers need to wait for
the production suite to get completed so that the backend test suite can
start which has a fairly large chances of being broken. Now, we run the
production test suite in last.
This commit is contained in:
Harshit Bansal 2017-06-23 18:47:24 +00:00 committed by Greg Price
parent a63fd95b6a
commit df3edbaf79
1 changed files with 4 additions and 4 deletions

View File

@ -48,10 +48,6 @@ matrix:
include: include:
- python: "3.4" - python: "3.4"
env: TEST_SUITE=static-analysis env: TEST_SUITE=static-analysis
- python: "3.4"
env: TEST_SUITE=production
- python: "2.7"
env: TEST_SUITE=production
- python: "2.7" - python: "2.7"
env: TEST_SUITE=frontend env: TEST_SUITE=frontend
- python: "3.4" - python: "3.4"
@ -60,6 +56,10 @@ matrix:
env: TEST_SUITE=backend env: TEST_SUITE=backend
- python: "3.4" - python: "3.4"
env: TEST_SUITE=backend env: TEST_SUITE=backend
- python: "2.7"
env: TEST_SUITE=production
- python: "3.4"
env: TEST_SUITE=production
sudo: required sudo: required
services: services:
- docker - docker