fe8c583e09
Attempt all of the CI
2022-04-27 07:53:30 +01:00
b0abbfacd4
Fix Docker build versioning ( #20077 )
...
* Centralise version scripts and fix Docker version
* Refactor generation of a git-hash-based version into get-version-from-git
* Refactor normalization of versions (stripping leading v) into normalize-version.sh
* Call get-version-from-git from ci_package.sh, call normalize-version from package.sh
* Refactor docker-write-version.sh into docker-package.sh, which both writes the
version file and invokes yarn build passing VERSION
* Normalize the version received from the server
2021-12-07 15:11:01 +11:00
f550d63198
Pass our VERSION to sentry plugin's release arg via env ( #19474 )
...
Use our existing VERSION, deduced by the packaging script, as the release for sentry sourcemaps.
This will be undefined for dev builds.
2021-10-22 15:06:14 +01:00
02ca5011a3
Updating package.sh
...
This should correct the tarball structure from `riot-$version` to `element-$version`.
2020-07-31 15:59:13 -05:00
ec66069e96
Update build scripts for new process
...
We have to convert *something* to TypeScript so it doesn't complain that there's nothing to compile, so this converts the easiest utility library.
Many of the scripts are copied from the react-sdk.
2020-01-08 16:09:42 -07:00
c62da0eda6
Don't fail if there's no local config to remove
...
The script has a set -e so don't fail if there's nothing to rm
2019-04-26 14:13:02 +01:00
8002d98f50
Remove config.json from package dir
2019-04-24 11:28:26 +01:00
1312ba537a
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 11:06:57 +00:00
cef26a5b20
fix #3894
2017-05-15 21:14:01 +01:00
f248477f82
stage 0.5 rebrand (rename dist release)
...
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-11 17:46:08 +01:00
61c338a233
remove leading v in /version file so its semver
...
and also then consistent with electron versioning
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
2017-05-02 21:32:27 +01:00
9ce2adceef
Include config.sample.json in dist tarball
...
Fixes https://github.com/vector-im/vector-web/issues/2607
2016-11-21 10:40:35 +00:00
6e47d2f1b5
It's '=' in sh, not '=='
2016-11-11 18:07:03 +00:00
3b06563960
Fix jenkins script / redeployer
...
and make them re-use the package script rather than doing their
own thing
2016-11-08 17:08:01 +00:00
5b7f629996
Build to the 'webapp' directory instead
...
People may have config files in vector/ so it would be nonideal
if we started overwriting them / blowing them away.
2016-11-08 15:46:21 +00:00
f5d95f7314
Use an env var for the package version
...
Because supplying arguments to npm scripts is a bad idea: it just
appends the arguments blindly to whatever the command was. Thanks,
npm.
2016-11-04 09:40:24 +00:00
d04cc03c1c
Take version from first arg, if given
2016-11-02 11:38:11 +00:00
f17e851435
Rename the package script/output dir to 'dist'
...
To match conventions from other projects and match the release
script which expects releasde artefacts in dist/
2016-11-01 15:22:06 +00:00
fa322e8488
Auto-create a sensible version file. Copy the vector dir so we can put it in there rather than creating files in the main vector dir.
2016-02-24 18:59:33 +00:00
874123bbfa
Move package script out and make it tar into a versioned top level directory. It may as well be a shell script since it's unix specific anyway, and maintaining it inside package.json is now impractical.
2016-02-24 18:41:30 +00:00
Michael Telatynski