OpenCloud
/
element-web
mirror of https://github.com/vector-im/element-web
1
0
Fork 0
Code Issues Releases Wiki Activity
element-web/.buildkite/pipeline.yaml

78 lines
2.0 KiB
YAML
Raw Normal View History

Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
steps:
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-09 00:09:26 +01:00
- label: ":eslint: JS Lint"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
command:
Fix buildkite pipeline
2020-01-09 00:14:01 +01:00
- "yarn install"
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-09 00:09:26 +01:00
- "yarn lint:js"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
plugins:
- docker#v3.0.1:
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-09 00:09:26 +01:00
image: "node:12"
# This layer doesn't have a TypeScript linter. This comment is to remind TravisR to fix that.
# - label: ":eslint: TS Lint"
# command:
# - "echo '--- Install js-sdk'"
# - "./scripts/ci/install-deps.sh"
# - "yarn lint:ts"
# plugins:
# - docker#v3.0.1:
# image: "node:12"
- label: ":eslint: Types Lint"
command:
Fix buildkite pipeline
2020-01-09 00:14:01 +01:00
- "yarn install"
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-09 00:09:26 +01:00
- "yarn lint:types"
plugins:
- docker#v3.0.1:
image: "node:12"
- label: "🛠 Build"
command:
Fix CI tests There's a bunch of generated files that webpack relies on to work, and Karma works off webpack. To make both happy we've added a new `build:genfiles` script which takes care of this for us. We also have to install and build our other layers to get the same effect (like generating the react-sdk's component index, while we still have one). This commit also fixes all the imports in the tests because they were just wrong. They should have been caught in the ES6ification earlier, but were missed.
2020-01-14 01:38:34 +01:00
- "echo '--- Fetching Dependencies'"
- "./scripts/fetch-develop.deps.sh --depth 1"
Fix buildkite pipeline
2020-01-09 00:14:01 +01:00
- "yarn install"
Fix CI tests There's a bunch of generated files that webpack relies on to work, and Karma works off webpack. To make both happy we've added a new `build:genfiles` script which takes care of this for us. We also have to install and build our other layers to get the same effect (like generating the react-sdk's component index, while we still have one). This commit also fixes all the imports in the tests because they were just wrong. They should have been caught in the ES6ification earlier, but were missed.
2020-01-14 01:38:34 +01:00
- "echo '+++ Building Project'"
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-09 00:09:26 +01:00
- "yarn build"
plugins:
- docker#v3.0.1:
image: "node:12"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
Swap over to Jest, breaking everything
2020-01-15 21:00:50 +01:00
- label: ":jest: Tests"
Use medium agents for the more resource intensive builds
2019-03-21 18:00:06 +01:00
agents:
# We use a medium sized instance instead of the normal small ones because
# webpack loves to gorge itself on resources.
queue: "medium"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
command:
Add log grouping to buildkite It mostly truncates the log anyway but what are you gonna do
2019-03-20 22:33:25 +01:00
- "echo '--- Fetching Dependencies'"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
- "./scripts/fetch-develop.deps.sh --depth 1"
- "yarn install"
Ensure autogenned files are present for tests
2020-01-15 22:52:26 +01:00
- "yarn build:genfiles" # We have to build the app to make sure the autogenned files are present
Add log grouping to buildkite It mostly truncates the log anyway but what are you gonna do
2019-03-20 22:33:25 +01:00
- "echo '+++ Running Tests'"
Add a basic BuildKite :pipeline:
2019-03-14 01:25:06 +01:00
- "yarn test"
plugins:
- docker#v3.0.1:
image: "node:10"
Try running packager with buildkite
2019-04-26 13:21:21 +02:00
consistent capitalisation in buildkite pipelines
2019-04-26 16:09:01 +02:00
- label: ":hammer: Package"
Try running packager with buildkite
2019-04-26 13:21:21 +02:00
command:
- "echo '--- Fetching Dependencies'"
- "./scripts/fetch-develop.deps.sh --depth 1"
- "yarn install"
- "echo '+++ Packaging'"
- "./scripts/ci_package.sh"
Only bother packaging the develop branch
2019-04-26 15:38:36 +02:00
branches: "develop"
Try running packager with buildkite
2019-04-26 13:21:21 +02:00
artifact_paths: "dist/riot-*.tar.gz"
plugins:
- docker#v3.0.1:
image: "node:10"
Verify i18n in CI
2019-07-11 20:45:06 +02:00
- label: "🌐 i18n"
command:
Fetch deps
2019-07-11 20:47:50 +02:00
- "echo '--- Fetching Dependencies'"
- "./scripts/fetch-develop.deps.sh --depth 1"
Verify i18n in CI
2019-07-11 20:45:06 +02:00
- "yarn install"
Fetch deps
2019-07-11 20:47:50 +02:00
- "echo '+++ Testing i18n output'"
Verify i18n in CI
2019-07-11 20:45:06 +02:00
- "yarn diff-i18n"
plugins:
- docker#v3.0.1:
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-09 00:09:26 +01:00
image: "node:10"