element-web/scripts/jenkins.sh

#!/bin/bash

set -e

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
nvm use 6

set -x

npm install

# apparently npm 3.10.3 on node 6.4.0 doesn't upgrade #develop target with npm install unless explicitly asked.
npm install matrix-react-sdk matrix-js-sdk olm

# install olm. A naive 'npm i ./olm/olm-*.tgz' fails because it uses the url
# from our package.json (or even matrix-js-sdk's) in preference.
#
# disabled for now, to avoid the annoying scenario of a release doing something
# different to /develop. Instead, add it to the 'npm install' list above.
# -- rav 2016/02/03
#tar -C olm -xz < olm/olm-*.tgz
#rm -r node_modules/olm
#cp -r olm/package node_modules/olm


# we may be using dev branches of js-sdk and react-sdk, in which case we need to build them
(cd node_modules/matrix-js-sdk && npm install)
(cd node_modules/matrix-react-sdk && npm install)

# run the mocha tests
npm run test

# run eslint
npm run lintall -- -f checkstyle -o eslint.xml || true

rm dist/vector-*.tar.gz || true # rm previous artifacts without failing if it doesn't exist

 # node_modules deps from 'npm install' don't have a .git dir so can't
 # rev-parse; but they do set the commit in package.json under 'gitHead' which
 # we're grabbing here.
REACT_SHA=$(grep 'gitHead' node_modules/matrix-react-sdk/package.json | cut -d \" -f 4 | head -c 12)
JSSDK_SHA=$(grep 'gitHead' node_modules/matrix-js-sdk/package.json | cut -d \" -f 4 | head -c 12)

VECTOR_SHA=$(git rev-parse --short=12 HEAD) # use the ACTUAL SHA rather than assume develop

DIST_VERSION=$VECTOR_SHA-react-$REACT_SHA-js-$JSSDK_SHA scripts/package.sh -d
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 16:31:04 +01:00			`#!/bin/bash`

			`set -e`

Don't hardcode home dir in jenkins script 2017-02-17 20:18:58 +01:00			`export NVM_DIR="$HOME/.nvm"`
Add jenkins.sh for builds 2016-02-02 16:44:41 +01:00			`[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"`
Switch to node 6 ... because 4 is ooold, and I'd like to use the same version on travis. 2016-08-25 15:25:05 +02:00			`nvm use 6`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 16:31:04 +01:00
			`set -x`

Add jenkins.sh for builds 2016-02-02 16:44:41 +01:00			`npm install`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 16:31:04 +01:00
try to unbreak jenkins >:( 2016-08-27 02:54:19 +02:00			`# apparently npm 3.10.3 on node 6.4.0 doesn't upgrade #develop target with npm install unless explicitly asked.`
Jenkins: use default olm ... to stop us making a release and realising we forgot to bump the olm version in vector-web. 2017-02-03 16:06:03 +01:00			`npm install matrix-react-sdk matrix-js-sdk olm`
try to unbreak jenkins >:( 2016-08-27 02:54:19 +02:00
Another go at using latest Olm The previous attempt failed due to npm shenanigans. Let's have another go, without the "help" of npm. 2016-09-06 14:24:06 +02:00			`# install olm. A naive 'npm i ./olm/olm-*.tgz' fails because it uses the url`
			`# from our package.json (or even matrix-js-sdk's) in preference.`
Jenkins: use default olm ... to stop us making a release and realising we forgot to bump the olm version in vector-web. 2017-02-03 16:06:03 +01:00			`#`
			`# disabled for now, to avoid the annoying scenario of a release doing something`
			`# different to /develop. Instead, add it to the 'npm install' list above.`
			`# -- rav 2016/02/03`
			`#tar -C olm -xz < olm/olm-*.tgz`
			`#rm -r node_modules/olm`
			`#cp -r olm/package node_modules/olm`

jenkins.sh: install olm from jenkins artifacts Use the latest version of olm, as provided by jenkins, rather than the most recent release. 2016-09-05 19:54:10 +02:00
Build the js-sdk in the CI script now it's transpiled 2017-01-11 18:20:27 +01:00			`# we may be using dev branches of js-sdk and react-sdk, in which case we need to build them`
Fix jenkins build Do `npm install` on js-sdk rather than `npm run build`, which will hopefully mean that `browserify` gets installed before we try to run it. The README says we should use `npm install` for the react-sdk too, so let's do that, and bring the travis and jenkins builds into sync with the README. 2017-02-01 17:11:11 +01:00			`(cd node_modules/matrix-js-sdk && npm install)`
			`(cd node_modules/matrix-react-sdk && npm install)`
Use npm to fetch react-sdk and js-sdk After some discussion, we've agreed it's less evil to have package.json point to git develop, even if you then have to do a manual build step. That avoids any future problems where (for example) js-sdk develop gains experimental changes which would break for users using a build process which involves a manual git checkout. 2016-03-11 15:30:53 +01:00
Run some tests under karma Including a regression test for https://github.com/vector-im/vector-web/issues/1314 2016-04-13 11:15:04 +02:00			`# run the mocha tests`
			`npm run test`

Make jenkins run the linter 2017-01-23 16:42:50 +01:00			`# run eslint`
			`npm run lintall -- -f checkstyle -o eslint.xml \|\| true`

dist now, not packages 2016-11-08 18:37:49 +01:00			`rm dist/vector-*.tar.gz \|\| true # rm previous artifacts without failing if it doesn't exist`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 16:31:04 +01:00
Use npm to fetch react-sdk and js-sdk After some discussion, we've agreed it's less evil to have package.json point to git develop, even if you then have to do a manual build step. That avoids any future problems where (for example) js-sdk develop gains experimental changes which would break for users using a build process which involves a manual git checkout. 2016-03-11 15:30:53 +01:00			`# node_modules deps from 'npm install' don't have a .git dir so can't`
			`# rev-parse; but they do set the commit in package.json under 'gitHead' which`
			`# we're grabbing here.`
			`REACT_SHA=$(grep 'gitHead' node_modules/matrix-react-sdk/package.json \| cut -d \" -f 4 \| head -c 12)`
			`JSSDK_SHA=$(grep 'gitHead' node_modules/matrix-js-sdk/package.json \| cut -d \" -f 4 \| head -c 12)`

Dump vector/react/jssdk SHAs in filename 2016-02-02 18:03:48 +01:00			`VECTOR_SHA=$(git rev-parse --short=12 HEAD) # use the ACTUAL SHA rather than assume develop`
Use npm to fetch react-sdk and js-sdk After some discussion, we've agreed it's less evil to have package.json point to git develop, even if you then have to do a manual build step. That avoids any future problems where (for example) js-sdk develop gains experimental changes which would break for users using a build process which involves a manual git checkout. 2016-03-11 15:30:53 +01:00
Don't include two vector prefixes 2016-11-11 19:23:25 +01:00			`DIST_VERSION=$VECTOR_SHA-react-$REACT_SHA-js-$JSSDK_SHA scripts/package.sh -d`