OpenCloud
/
element-web
mirror of https://github.com/vector-im/element-web
1
0
Fork 0
Code Issues Releases Wiki Activity
element-web/scripts/ci/app-tests.sh

13 lines
284 B
Bash
Raw Normal View History

run both react-sdk and riot-web tests
2019-01-09 15:16:20 +01:00
#!/bin/bash
#
Add basic BuildKite :pipeline:
2019-03-14 00:42:05 +01:00
# script which is run by the CI build (after `yarn test`).
run both react-sdk and riot-web tests
2019-01-09 15:16:20 +01:00
#
Rebrand various CI scripts and modules This replaces Riot with Element in various CI scripts, modules, parameters, etc. This _should_ be the last major rebranding pass (hopefully). Fixes https://github.com/vector-im/element-web/issues/14894
2020-12-03 14:56:27 +01:00
# clones element-web develop and runs the tests against our version of react-sdk.
run both react-sdk and riot-web tests
2019-01-09 15:16:20 +01:00
set -ev
Rebrand various CI scripts and modules This replaces Riot with Element in various CI scripts, modules, parameters, etc. This _should_ be the last major rebranding pass (hopefully). Fixes https://github.com/vector-im/element-web/issues/14894
2020-12-03 14:56:27 +01:00
scripts/ci/layered.sh
Nest other layers inside on automation This changes the nesting style because some CI / CD systems do not allow moving to a directory above the checkout for the primary repo (`react-sdk` in this case). Part of https://github.com/vector-im/element-web/issues/12624
2020-11-20 18:55:48 +01:00
cd element-web
Ensure generated files are present for riot-web tests
2020-01-21 18:53:17 +01:00
yarn build:genfiles # so the tests can run. Faster version of `build`
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best.
2019-03-11 15:22:02 +01:00
yarn test