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

34 lines
1.1 KiB
Bash
Raw Normal View History

Use js-sdk and react-sdk from jenkins artifacts
2016-02-25 16:31:04 +01:00
#!/bin/bash
set -e
Add jenkins.sh for builds
2016-02-02 16:44:41 +01:00
export NVM_DIR="/home/jenkins/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"
nvm use 4
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
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
# we may be using a dev branch of react-sdk, in which case we need to build it
(cd node_modules/matrix-react-sdk && npm run build)
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
Use js-sdk and react-sdk from jenkins artifacts
2016-02-25 16:31:04 +01:00
# build our artifacts; dumps them in ./vector
Do less mangling of jenkins builds This turns off uglification, and turns on the react sanity checks.
2016-04-14 16:05:36 +02:00
npm run build:dev
Dump vector/react/jssdk SHAs in filename
2016-02-02 18:03:48 +01:00
# gzip up ./vector
Update jenkins.sh to include the git commit
2016-02-02 17:09:33 +01:00
rm 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
Dump vector/react/jssdk SHAs in filename
2016-02-02 18:03:48 +01:00
tar -zcvhf vector-$VECTOR_SHA-react-$REACT_SHA-js-$JSSDK_SHA.tar.gz vector #g[z]ip, [c]reate archive, [v]erbose, [f]ilename, [h]ard-dereference (do not archive symlinks)