schildi-web/scripts/ci_package.sh

#!/bin/bash

# Runs package.sh setting the version to git hashes of the riot-web,
# react-sdk & js-sdk checkouts, for the case where these dependencies
# are git checkouts.

set -ex

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 10:31:04 -05:00			`#!/bin/bash`

Change jenkins script to package script Take the useful part of the jenkins script and put it in a script that makes a package with the git hashes as its version. 2019-04-26 06:25:41 -04:00			`# Runs package.sh setting the version to git hashes of the riot-web,`
			`# react-sdk & js-sdk checkouts, for the case where these dependencies`
			`# are git checkouts.`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 10:31:04 -05:00
combine sets 2019-04-26 07:22:32 -04:00			`set -ex`
Use js-sdk and react-sdk from jenkins artifacts 2016-02-25 10:31:04 -05:00
stage 0.5 rebrand (rename dist release) Signed-off-by: Michael Telatynski <7t3chguy@gmail.com> 2017-05-11 12:46:08 -04: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 10:31:04 -05:00
rev-parse the commit from the deps Because it's not added to package.json by npm anymore 2017-05-26 17:51:55 -04: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 09:30:53 -05:00
Dump vector/react/jssdk SHAs in filename 2016-02-02 12:03:48 -05: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 09:30:53 -05:00
Don't include two vector prefixes 2016-11-11 13:23:25 -05:00			`DIST_VERSION=$VECTOR_SHA-react-$REACT_SHA-js-$JSSDK_SHA scripts/package.sh -d`