riot-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`

yarn link

scripts/fetchdep.sh vector-im riot-web

pushd "$RIOT_WEB_DIR"

yarn link matrix-js-sdk
yarn link matrix-react-sdk

yarn install

yarn build

popd
Configure travis to test riot-web after building 2017-01-19 13:51:20 +01: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 15:22:02 +01:00			# script which is run by the travis build (after `yarn test`).
Configure travis to test riot-web after building 2017-01-19 13:51:20 +01: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 19:23:34 +01:00			`RIOT_WEB_DIR=riot-web`
			REACT_SDK_DIR=`pwd`

Reorder link and install steps Take advantage of Yarn's preservation of links while installing and set up links first and install second. This should result in a small speedup since we no longer install the published SDKs just to replace them on the next line. 2019-03-11 19:08:37 +01:00			`yarn link`

Use the right js-sdk branch when testing On the react-sdk tests not just riot-web 2018-05-02 11:58:43 +02:00			`scripts/fetchdep.sh vector-im riot-web`
Do riot-web setup in a different order ... in an effort to stop npm cocking it up. 2017-01-19 19:23:34 +01:00
Reorder link and install steps Take advantage of Yarn's preservation of links while installing and set up links first and install second. This should result in a small speedup since we no longer install the published SDKs just to replace them on the next line. 2019-03-11 19:08:37 +01:00			`pushd "$RIOT_WEB_DIR"`
Install source-map-loader before building riot-web 2017-01-19 18:41:58 +01:00
Reorder link and install steps Take advantage of Yarn's preservation of links while installing and set up links first and install second. This should result in a small speedup since we no longer install the published SDKs just to replace them on the next line. 2019-03-11 19:08:37 +01:00			`yarn link matrix-js-sdk`
			`yarn link matrix-react-sdk`
Install source-map-loader before building riot-web 2017-01-19 18:41:58 +01:00
Reorder link and install steps Take advantage of Yarn's preservation of links while installing and set up links first and install second. This should result in a small speedup since we no longer install the published SDKs just to replace them on the next line. 2019-03-11 19:08:37 +01:00			`yarn install`
Install source-map-loader before building riot-web 2017-01-19 18:41:58 +01: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 15:22:02 +01:00			`yarn build`
Reorder link and install steps Take advantage of Yarn's preservation of links while installing and set up links first and install second. This should result in a small speedup since we no longer install the published SDKs just to replace them on the next line. 2019-03-11 19:08:37 +01:00
try to run e2e tests in travis 2018-07-27 14:36:47 +02:00			`popd`