- 03 Dec, 2016 1 commit
-
-
Brian Jacobel committed
-
- 01 Dec, 2016 1 commit
-
-
Calen Pennington committed
-
- 29 Nov, 2016 1 commit
-
-
noraiz-anwar committed
-
- 28 Nov, 2016 2 commits
-
-
Ben Patterson committed
-
Ben Patterson committed
-
- 22 Nov, 2016 1 commit
-
-
Andy Armstrong committed
-
- 17 Nov, 2016 1 commit
-
-
Ben Patterson committed
-
- 16 Nov, 2016 2 commits
-
-
Ben Patterson committed
-
Problem: Intermittent "cb() never called!" errors on npm installs for platform. This is likely due to a race condition on installing OS-specific bits that are built during time of install. When more than one compilation takes place at one time, this error can occur. Workaround: Detect the error and re-run the install. (When retrying, one or all of the bits have been compiled. So running it again just finishes the install.)
Ben Patterson committed
-
- 15 Nov, 2016 1 commit
-
-
Calen Pennington committed
-
- 10 Nov, 2016 1 commit
-
-
This change: * gives us the flexibility of managing node from pull-request to pull-request. It'll be a huge lift to folks that want to test out node upgrades like @bjacobel or @andy-armstrong * Sets us up for a port to Xenial, which will be accomplished in part by using nodeenv for managing the node environment. See a companion PR on the configuration repo for edxapp: edx/configuration#3444 This pull request does not: * Attempt to solve any stability issues in builds related to node. * Make node installs any faster * Create any caching infrastructure to speed up node installs. They will be approximately as fast as they were before. Downloading the node bits build-to-build adds about 3 seconds, which is worth it for the added flexibility.
Ben Patterson committed
-
- 01 Nov, 2016 1 commit
-
-
stu committed
-
- 27 Oct, 2016 1 commit
-
-
Ben Patterson committed
-
- 26 Oct, 2016 1 commit
-
-
Jesse Zoldak committed
-
- 17 Oct, 2016 1 commit
-
-
Jesse Zoldak committed
-
- 14 Oct, 2016 1 commit
-
-
moment-timezone require config jasmine test fix, duplicate req. cleanup
Greg Martin committed
-
- 12 Oct, 2016 1 commit
-
-
Rendering model states when running migrate in Django 1.8 consumes on the order of 4x-6x more memory than <1.8. References: * https://code.djangoproject.com/ticket/24745 * https://code.djangoproject.com/ticket/24743 This is causing failures in Jenkins as the workers run out of memory and either processes cannot fork or the Out Of Memory Killer kills a process that is running tests. Disabling migrations until we do either or both of these: * Upgrade to Django 1.9 and turn them back on. See EV-92 "Discovery: Upgrade edx-platform to Django 1.9" * Address TE-1310 "Unit tests should be able to run without migrations"
Jesse Zoldak committed
-
- 06 Oct, 2016 1 commit
-
-
Andy Armstrong committed
-
- 07 Sep, 2016 1 commit
-
-
David committed
-
- 19 Aug, 2016 1 commit
-
-
Jesse Zoldak committed
-
- 18 Aug, 2016 1 commit
-
-
Calen Pennington committed
-
- 15 Aug, 2016 3 commits
-
-
David Baumgold committed
-
David Baumgold committed
-
David Baumgold committed
-
- 10 Aug, 2016 1 commit
-
-
Andy Armstrong committed
-
- 03 Aug, 2016 6 commits
-
-
Use @needs to specify task composition for paver service checks, so that arguments are bundled correctly
Calen Pennington committed -
Calen Pennington committed
-
Calen Pennington committed
-
Calen Pennington committed
-
This reverts commit acf50c44.
Calen Pennington committed -
Ned Batchelder committed
-
- 02 Aug, 2016 1 commit
-
-
Brian Jacobel committed
-
- 29 Jul, 2016 3 commits
-
-
Brian Jacobel committed
-
Brian Jacobel committed
-
Ben Patterson committed
-
- 27 Jul, 2016 1 commit
-
-
Saleem Latif committed
-
- 26 Jul, 2016 1 commit
-
-
This reverts commit ed80381b, reversing changes made to 205cb8b3.
Calen Pennington committed
-
- 22 Jul, 2016 3 commits
-
-
Calen Pennington committed
-
Calen Pennington committed
-
Calen Pennington committed
-