element-web/scripts/travis/build.sh

#!/bin/bash
#
# script which is run by the travis build (after `yarn test`).
#
# clones riot-web develop and runs the tests against our version of react-sdk.

set -ev

RIOT_WEB_DIR=riot-web
REACT_SDK_DIR=`pwd`

scripts/fetchdep.sh vector-im riot-web
pushd "$RIOT_WEB_DIR"

mkdir node_modules
yarn install

# use the version of js-sdk we just used in the react-sdk tests
rm -r node_modules/matrix-js-sdk
ln -s "$REACT_SDK_DIR/node_modules/matrix-js-sdk" node_modules/matrix-js-sdk

# ... and, of course, the version of react-sdk we just built
rm -r node_modules/matrix-react-sdk
ln -s "$REACT_SDK_DIR" node_modules/matrix-react-sdk

yarn build
popd
Configure travis to test riot-web after building 2017-01-19 12:51:20 +00:00			`#!/bin/bash`
			`#`
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 14:22:02 +00:00			# script which is run by the travis build (after `yarn test`).
Configure travis to test riot-web after building 2017-01-19 12:51:20 +00:00			`#`
			`# clones riot-web develop and runs the tests against our version of react-sdk.`

			`set -ev`

Do riot-web setup in a different order ... in an effort to stop npm cocking it up. 2017-01-19 18:23:34 +00:00			`RIOT_WEB_DIR=riot-web`
			REACT_SDK_DIR=`pwd`

Use the right js-sdk branch when testing On the react-sdk tests not just riot-web 2018-05-02 09:58:43 +00:00			`scripts/fetchdep.sh vector-im riot-web`
try to run e2e tests in travis 2018-07-27 12:36:47 +00:00			`pushd "$RIOT_WEB_DIR"`
Do riot-web setup in a different order ... in an effort to stop npm cocking it up. 2017-01-19 18:23:34 +00:00
Configure travis to test riot-web after building 2017-01-19 12:51:20 +00:00			`mkdir node_modules`
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 14:22:02 +00:00			`yarn install`
Install source-map-loader before building riot-web 2017-01-19 17:41:58 +00:00
Run the riot-web tests against js-sdk develop When running the riot-web builds, use the develop version of js-sdk instead of the latest release, to improve our chances of compatibility. 2017-07-05 14:43:33 +00:00			`# use the version of js-sdk we just used in the react-sdk tests`
			`rm -r node_modules/matrix-js-sdk`
			`ln -s "$REACT_SDK_DIR/node_modules/matrix-js-sdk" node_modules/matrix-js-sdk`
Install source-map-loader before building riot-web 2017-01-19 17:41:58 +00:00
Run the riot-web tests against js-sdk develop When running the riot-web builds, use the develop version of js-sdk instead of the latest release, to improve our chances of compatibility. 2017-07-05 14:43:33 +00:00			`# ... and, of course, the version of react-sdk we just built`
Do riot-web setup in a different order ... in an effort to stop npm cocking it up. 2017-01-19 18:23:34 +00:00			`rm -r node_modules/matrix-react-sdk`
			`ln -s "$REACT_SDK_DIR" node_modules/matrix-react-sdk`
Install source-map-loader before building riot-web 2017-01-19 17:41:58 +00:00
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 14:22:02 +00:00			`yarn build`
try to run e2e tests in travis 2018-07-27 12:36:47 +00:00			`popd`