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 10

set -x

# check out corresponding branches of dependencies.
# clone the deps with depth 1: we know we will only ever need that one commit.
`dirname $0`/fetch-develop.deps.sh --depth 1

yarn install

# run the mocha tests
#yarn test

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

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

# Since the deps are fetched from git, we can rev-parse
REACT_SHA=$(cd node_modules/matrix-react-sdk; git rev-parse --short=12 HEAD)
JSSDK_SHA=$(cd node_modules/matrix-js-sdk; git rev-parse --short=12 HEAD)

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`

Update jenkins.sh 2019-04-17 20:18:05 +02:00			`#export NVM_DIR="$HOME/.nvm"`
			`#[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"`
			`#nvm use 10`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 16:31:04 +01:00
			`set -x`

Jenkins.sh: only fetch head of dependency branches 2017-08-08 10:47:03 +02:00			`# check out corresponding branches of dependencies.`
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-12 12:06:57 +01:00			`# clone the deps with depth 1: we know we will only ever need that one commit.`
Jenkins.sh: only fetch head of dependency branches 2017-08-08 10:47:03 +02:00			`dirname $0`/fetch-develop.deps.sh --depth 1
Use fetch dep script in jenkins script 2017-05-17 17:17:08 +02: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-12 12:06:57 +01:00			`yarn install`
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
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`
Update jenkins.sh 2019-04-17 20:22:40 +02:00			`#yarn test`
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
Make jenkins run the linter 2017-01-23 16:42:50 +01:00			`# run eslint`
Update jenkins.sh 2019-04-17 20:22:40 +02:00			`#yarn lintall -- -f checkstyle -o eslint.xml \|\| true`
Make jenkins run the linter 2017-01-23 16:42:50 +01:00
stage 0.5 rebrand (rename dist release) Signed-off-by: Michael Telatynski <7t3chguy@gmail.com> 2017-05-11 18:46:08 +02:00			`rm dist/riot-*.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
rev-parse the commit from the deps Because it's not added to package.json by npm anymore 2017-05-26 23:51:55 +02:00			`# Since the deps are fetched from git, we can rev-parse`
			`REACT_SHA=$(cd node_modules/matrix-react-sdk; git rev-parse --short=12 HEAD)`
			`JSSDK_SHA=$(cd node_modules/matrix-js-sdk; git rev-parse --short=12 HEAD)`
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			`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`