Court Ewing 38d5fc5051 Isolate esvm clusters by purpose ... Attempting to run multiple elasticsearch clusters on the same host without specifying different cluster names actually triggers the discovery behaviors of elasticsearch, which adds the second es process as another node of the original cluster. This means that despite running on different ports, our test setups of elasticsearch actually attempt to modify the main dev setup. Fixes #5529		2015-12-02 21:20:56 +00:00
..
build	Merge branch 'preventHomeDirAccess'	2015-11-06 16:56:12 -06:00
config	Isolate esvm clusters by purpose	2015-12-02 21:20:56 +00:00
utils	[build] move to absolute paths and improve fpm/pleaserun support	2015-08-14 13:27:41 -07:00
downloadSelenium.js	[functional testing] Always check selenium hash	2015-09-17 11:56:36 -05:00
jenkins.js	Use esvm to start and stop elasticsearch for all tests that need it	2015-09-10 14:57:54 -04:00
licenses.js	[build] initial fix	2015-08-13 21:16:54 -07:00
lintStagedFiles.js	syntax change, output staged file count	2015-08-13 13:21:04 -07:00
plugin.js	switch to eslint	2015-07-31 17:16:09 -07:00
release.js	Remove npm shrinkwrap tasks	2015-09-17 17:57:46 -04:00
test.js	[functional testing] Load scenarios	2015-10-14 15:33:25 -05:00
travis.js	Use esvm to start and stop elasticsearch for all tests that need it	2015-09-10 14:57:54 -04:00