Andal.LND/edx-platform
6
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Introduce another bok-choy shard.

Browse Source 
Bok choy will now be broken as follows:
* shard 1
* shard 2
* shard 3
* default shard (i.e. 'none of the above')

We use our shards to break up work and reduce overall test time by leveraging
multiple test systems.
This commit is contained in:
Ben Patterson
2015-01-29 09:15:00 -05:00
parent beb9602d2a
commit 73b6f3f8a0
5 changed files with 35 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
scripts/all-tests.sh
View File

@@ -175,12 +175,17 @@ END
;;
"3")
paver test_bokchoy --extra_args="-a shard_1=False,shard_2=False"
paver test_bokchoy --extra_args="-a 'shard_3'"
paver bokchoy_coverage
;;
"4")
paver test_bokchoy --extra_args="-a shard_1=False,shard_2=False,shard_3=False"
paver bokchoy_coverage
;;
# Default case because if we later define another bok-choy shard on Jenkins
# (e.g. Shard 4) in the multi-config project and expand this file
# (e.g. Shard 5) in the multi-config project and expand this file
# with an additional case condition, old branches without that commit
# would not execute any tests on the worker assigned to that shard
# and thus their build would fail.