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

37 lines
591 B
Bash
Raw Normal View History

jenkins.sh for react-sdk
2016-02-25 15:18:26 +01:00
#!/bin/bash
set -e
Oops, un-hardcode correctly
2017-02-17 20:27:50 +01:00
export NVM_DIR="$HOME/.nvm"
jenkins.sh for react-sdk
2016-02-25 15:18:26 +01:00
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
Let's use a version of node we can download rather than dig up
2018-11-21 19:53:18 +01:00
nvm use 10
jenkins.sh for react-sdk
2016-02-25 15:18:26 +01:00
set -x
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
scripts/fetchdep.sh matrix-org matrix-js-sdk
pushd matrix-js-sdk
yarn link
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 install
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
popd
jenkins.sh for react-sdk
2016-02-25 15:18:26 +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
# install the other dependencies
yarn install
Build the js-sdk in the CI script now it's transpiled
2017-01-11 18:18:37 +01:00
Run mocha tests on jenkins
2016-03-29 00:37:00 +02:00
# run the mocha tests
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 --no-colors
Run mocha tests on jenkins
2016-03-29 00:37:00 +02:00
Run eslint in jenkins script
2016-07-01 20:38:14 +02:00
# run eslint
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 lintall -f checkstyle -o eslint.xml || true
Run eslint in jenkins script
2016-07-01 20:38:14 +02:00
Make travis/jenkins check for lint on files which are clean to start with
2017-06-08 14:52:52 +02:00
# re-run the linter, excluding any files known to have errors or warnings.
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 lintwithexclusions
Make travis/jenkins check for lint on files which are clean to start with
2017-06-08 14:52:52 +02:00
Remove old tarball before building new one
2016-02-25 18:24:13 +01:00
# delete the old tarball, if it exists
rm -f matrix-react-sdk-*.tgz
jenkins.sh for react-sdk
2016-02-25 15:18:26 +01:00
# build our tarball
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 pack