|
|
|
|
version: 2.1
|
|
|
|
|
|
|
|
|
|
executors:
|
|
|
|
|
node-browsers:
|
|
|
|
|
docker:
|
|
|
|
|
- image: circleci/node:14-browsers
|
|
|
|
|
node-browsers-medium-plus:
|
|
|
|
|
docker:
|
|
|
|
|
- image: circleci/node:14-browsers
|
|
|
|
|
resource_class: medium+
|
|
|
|
|
environment:
|
|
|
|
|
NODE_OPTIONS: --max_old_space_size=2048
|
|
|
|
|
shellcheck:
|
|
|
|
|
docker:
|
|
|
|
|
- image: koalaman/shellcheck-alpine@sha256:35882cba254810c7de458528011e935ba2c4f3ebcb224275dfa7ebfa930ef294
|
|
|
|
|
|
|
|
|
|
workflows:
|
|
|
|
|
test_and_release:
|
|
|
|
|
jobs:
|
|
|
|
|
- create_release_pull_request:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
filters:
|
|
|
|
|
branches:
|
|
|
|
|
only:
|
|
|
|
|
- /^Version-v(\d+)[.](\d+)[.](\d+)/
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- test-deps
|
|
|
|
|
- validate-lavamoat-config:
|
|
|
|
|
filters:
|
|
|
|
|
branches:
|
|
|
|
|
only:
|
|
|
|
|
- /^Version-v(\d+)[.](\d+)[.](\d+)|master/
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- prep-build:
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- prep-build-test:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- prep-build-test-metrics:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- prep-build-storybook:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- test-lint:
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- test-lint-shellcheck
|
|
|
|
|
- test-lint-lockfile:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- test-lint-changelog:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- test-e2e-chrome:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-test
|
|
|
|
|
- test-e2e-firefox:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-test
|
|
|
|
|
- test-e2e-chrome-metrics:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-test-metrics
|
|
|
|
|
- test-e2e-firefox-metrics:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-test-metrics
|
|
|
|
|
- test-unit:
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- test-unit-global:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-deps
|
|
|
|
|
- validate-source-maps:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build
|
|
|
|
|
- test-mozilla-lint:
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- prep-build
|
|
|
|
|
- all-tests-pass:
|
|
|
|
|
requires:
|
|
|
|
|
- validate-lavamoat-config
|
|
|
|
|
- test-lint
|
|
|
|
|
- test-lint-shellcheck
|
|
|
|
|
- test-lint-lockfile
|
|
|
|
|
- test-lint-changelog
|
|
|
|
|
- test-unit
|
|
|
|
|
- test-unit-global
|
|
|
|
|
- validate-source-maps
|
|
|
|
|
- test-mozilla-lint
|
|
|
|
|
- test-e2e-chrome
|
|
|
|
|
- test-e2e-firefox
|
|
|
|
|
- test-e2e-chrome-metrics
|
|
|
|
|
- test-e2e-firefox-metrics
|
|
|
|
|
- benchmark:
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-test
|
|
|
|
|
- job-publish-prerelease:
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- prep-build
|
|
|
|
|
- prep-build-storybook
|
|
|
|
|
- benchmark
|
|
|
|
|
- all-tests-pass
|
|
|
|
|
- job-publish-release:
|
|
|
|
|
filters:
|
|
|
|
|
branches:
|
|
|
|
|
only: master
|
|
|
|
|
requires:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
- prep-deps
|
|
|
|
|
- prep-build
|
|
|
|
|
- all-tests-pass
|
|
|
|
|
- job-publish-storybook:
|
|
|
|
|
filters:
|
|
|
|
|
branches:
|
|
|
|
|
only: develop
|
|
|
|
|
requires:
|
|
|
|
|
- prep-build-storybook
|
|
|
|
|
|
|
|
|
|
jobs:
|
|
|
|
|
create_release_pull_request:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Bump manifest version
|
|
|
|
|
command: .circleci/scripts/release-bump-manifest-version.sh
|
|
|
|
|
- run:
|
|
|
|
|
name: Update changelog
|
|
|
|
|
command: yarn update-changelog --rc
|
|
|
|
|
- run:
|
|
|
|
|
name: Commit changes
|
|
|
|
|
command: .circleci/scripts/release-commit-version-bump.sh
|
|
|
|
|
- run:
|
|
|
|
|
name: Create GitHub Pull Request for version
|
|
|
|
|
command: .circleci/scripts/release-create-release-pr.sh
|
|
|
|
|
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
prep-deps:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- restore_cache:
|
|
|
|
|
key: dependency-cache-v1-{{ checksum "yarn.lock" }}
|
|
|
|
|
- run:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
name: Install deps
|
|
|
|
|
command: |
|
|
|
|
|
.circleci/scripts/deps-install.sh
|
|
|
|
|
- save_cache:
|
|
|
|
|
key: dependency-cache-v1-{{ checksum "yarn.lock" }}
|
|
|
|
|
paths:
|
|
|
|
|
- node_modules/
|
|
|
|
|
- build-artifacts/yarn-install-har/
|
|
|
|
|
- run:
|
|
|
|
|
name: Postinstall
|
|
|
|
|
command: |
|
|
|
|
|
yarn setup:postinstall
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- node_modules
|
|
|
|
|
- build-artifacts
|
|
|
|
|
|
|
|
|
|
validate-lavamoat-config:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Validate allow-scripts config
|
|
|
|
|
command: |
|
|
|
|
|
.circleci/scripts/validate-allow-scripts.sh
|
|
|
|
|
- run:
|
|
|
|
|
name: Validate LavaMoat policy
|
|
|
|
|
command: |
|
|
|
|
|
.circleci/scripts/validate-lavamoat-policy.sh
|
|
|
|
|
|
|
|
|
|
prep-build:
|
|
|
|
|
executor: node-browsers-medium-plus
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: build:dist
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
command: yarn dist
|
|
|
|
|
- run:
|
|
|
|
|
name: build:debug
|
|
|
|
|
command: find dist/ -type f -exec md5sum {} \; | sort -k 2
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- dist
|
|
|
|
|
- builds
|
|
|
|
|
|
|
|
|
|
prep-build-test:
|
|
|
|
|
executor: node-browsers-medium-plus
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Build extension for testing
|
|
|
|
|
command: yarn build:test
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to 'dist-test' to avoid conflict with production build
|
|
|
|
|
command: mv ./dist ./dist-test
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to 'builds-test' to avoid conflict with production build
|
|
|
|
|
command: mv ./builds ./builds-test
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- dist-test
|
|
|
|
|
- builds-test
|
|
|
|
|
|
|
|
|
|
prep-build-test-metrics:
|
|
|
|
|
executor: node-browsers-medium-plus
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Build extension for testing metrics
|
|
|
|
|
command: yarn build:test:metrics
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to 'dist-test-metrics' to avoid conflict with production build
|
|
|
|
|
command: mv ./dist ./dist-test-metrics
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to 'builds-test' to avoid conflict with production build
|
|
|
|
|
command: mv ./builds ./builds-test-metrics
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- dist-test-metrics
|
|
|
|
|
- builds-test-metrics
|
|
|
|
|
|
|
|
|
|
prep-build-storybook:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Build Storybook
|
|
|
|
|
command: yarn storybook:build
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- storybook-build
|
|
|
|
|
|
|
|
|
|
test-lint:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Lint
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
command: yarn lint
|
|
|
|
|
- run:
|
|
|
|
|
name: Verify locales
|
|
|
|
|
command: yarn verify-locales --quiet
|
|
|
|
|
|
|
|
|
|
test-lint-shellcheck:
|
|
|
|
|
executor: shellcheck
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run: apk add --no-cache bash jq yarn
|
|
|
|
|
- run:
|
|
|
|
|
name: ShellCheck Lint
|
|
|
|
|
command: ./development/shellcheck.sh
|
|
|
|
|
|
|
|
|
|
test-lint-lockfile:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: lockfile-lint
|
|
|
|
|
command: yarn lint:lockfile
|
|
|
|
|
|
|
|
|
|
test-lint-changelog:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- when:
|
|
|
|
|
condition:
|
|
|
|
|
not:
|
|
|
|
|
matches:
|
|
|
|
|
pattern: /^Version-v(\d+)[.](\d+)[.](\d+)$/
|
|
|
|
|
value: << pipeline.git.branch >>
|
|
|
|
|
steps:
|
|
|
|
|
- run:
|
|
|
|
|
name: Validate changelog
|
|
|
|
|
command: yarn auto-changelog validate
|
|
|
|
|
- when:
|
|
|
|
|
condition:
|
|
|
|
|
matches:
|
|
|
|
|
pattern: /^Version-v(\d+)[.](\d+)[.](\d+)$/
|
|
|
|
|
value: << pipeline.git.branch >>
|
|
|
|
|
steps:
|
|
|
|
|
- run:
|
|
|
|
|
name: Validate release candidate changelog
|
|
|
|
|
command: yarn auto-changelog validate --rc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
test-deps:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
name: yarn audit
|
|
|
|
|
command: .circleci/scripts/yarn-audit.sh
|
|
|
|
|
|
|
|
|
|
test-e2e-chrome:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run:
|
|
|
|
|
name: Re-Install Chrome
|
|
|
|
|
command: ./.circleci/scripts/chrome-install.sh
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to dist
|
|
|
|
|
command: mv ./dist-test ./dist
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to builds
|
|
|
|
|
command: mv ./builds-test ./builds
|
|
|
|
|
- run:
|
|
|
|
|
name: test:e2e:chrome
|
|
|
|
|
command: |
|
|
|
|
|
if .circleci/scripts/test-run-e2e.sh
|
|
|
|
|
then
|
|
|
|
|
yarn test:e2e:chrome
|
|
|
|
|
fi
|
|
|
|
|
no_output_timeout: 20m
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
|
|
|
|
|
test-e2e-chrome-metrics:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run:
|
|
|
|
|
name: Re-Install Chrome
|
|
|
|
|
command: ./.circleci/scripts/chrome-install.sh
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to dist
|
|
|
|
|
command: mv ./dist-test-metrics ./dist
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to builds
|
|
|
|
|
command: mv ./builds-test-metrics ./builds
|
|
|
|
|
- run:
|
|
|
|
|
name: test:e2e:chrome:metrics
|
|
|
|
|
command: |
|
|
|
|
|
if .circleci/scripts/test-run-e2e.sh
|
|
|
|
|
then
|
|
|
|
|
yarn test:e2e:chrome:metrics
|
|
|
|
|
fi
|
|
|
|
|
no_output_timeout: 20m
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
|
|
|
|
|
test-e2e-firefox:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run:
|
|
|
|
|
name: Install Firefox
|
|
|
|
|
command: ./.circleci/scripts/firefox-install.sh
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to dist
|
|
|
|
|
command: mv ./dist-test ./dist
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to builds
|
|
|
|
|
command: mv ./builds-test ./builds
|
|
|
|
|
- run:
|
|
|
|
|
name: test:e2e:firefox
|
|
|
|
|
command: |
|
|
|
|
|
if .circleci/scripts/test-run-e2e.sh
|
|
|
|
|
then
|
|
|
|
|
yarn test:e2e:firefox
|
|
|
|
|
fi
|
|
|
|
|
no_output_timeout: 20m
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
|
|
|
|
|
test-e2e-firefox-metrics:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run:
|
|
|
|
|
name: Install Firefox
|
|
|
|
|
command: ./.circleci/scripts/firefox-install.sh
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to dist
|
|
|
|
|
command: mv ./dist-test-metrics ./dist
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to builds
|
|
|
|
|
command: mv ./builds-test-metrics ./builds
|
|
|
|
|
- run:
|
|
|
|
|
name: test:e2e:firefox:metrics
|
|
|
|
|
command: |
|
|
|
|
|
if .circleci/scripts/test-run-e2e.sh
|
|
|
|
|
then
|
|
|
|
|
yarn test:e2e:firefox:metrics
|
|
|
|
|
fi
|
|
|
|
|
no_output_timeout: 20m
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
|
|
|
|
|
benchmark:
|
|
|
|
|
executor: node-browsers-medium-plus
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- run:
|
|
|
|
|
name: Re-Install Chrome
|
|
|
|
|
command: ./.circleci/scripts/chrome-install.sh
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test build to dist
|
|
|
|
|
command: mv ./dist-test ./dist
|
|
|
|
|
- run:
|
|
|
|
|
name: Move test zips to builds
|
|
|
|
|
command: mv ./builds-test ./builds
|
|
|
|
|
- run:
|
|
|
|
|
name: Run page load benchmark
|
|
|
|
|
command: yarn benchmark:chrome --out test-artifacts/chrome/benchmark/pageload.json
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- test-artifacts
|
|
|
|
|
|
|
|
|
|
job-publish-prerelease:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: build:source-map-explorer
|
|
|
|
|
command: ./development/source-map-explorer.sh
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: dist/sourcemaps
|
|
|
|
|
destination: builds/sourcemaps
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: builds
|
|
|
|
|
destination: builds
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: coverage
|
|
|
|
|
destination: coverage
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: jest-coverage
|
|
|
|
|
destination: jest-coverage
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: test-artifacts
|
|
|
|
|
destination: test-artifacts
|
|
|
|
|
# important: generate lavamoat viz AFTER uploading builds as artifacts
|
|
|
|
|
# Temporarily disabled until we can update to a version of `sesify` with
|
|
|
|
|
# this fix included: https://github.com/LavaMoat/LavaMoat/pull/121
|
|
|
|
|
- run:
|
|
|
|
|
name: build:lavamoat-viz
|
|
|
|
|
command: ./.circleci/scripts/create-lavamoat-viz.sh
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: build-artifacts
|
|
|
|
|
destination: build-artifacts
|
|
|
|
|
- store_artifacts:
|
|
|
|
|
path: storybook-build
|
|
|
|
|
destination: storybook
|
|
|
|
|
- run:
|
|
|
|
|
name: build:announce
|
|
|
|
|
command: ./development/metamaskbot-build-announce.js
|
|
|
|
|
|
|
|
|
|
job-publish-release:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: sentry sourcemaps upload
|
|
|
|
|
command: SENTRY_ORG=metamask SENTRY_PROJECT=metamask yarn sentry:publish
|
|
|
|
|
- run:
|
|
|
|
|
name: Create GitHub release
|
|
|
|
|
command: |
|
|
|
|
|
.circleci/scripts/release-create-gh-release.sh
|
|
|
|
|
|
|
|
|
|
job-publish-storybook:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- add_ssh_keys:
|
|
|
|
|
fingerprints:
|
|
|
|
|
- "3d:49:29:f4:b2:e8:ea:af:d1:32:eb:2a:fc:15:85:d8"
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: storybook:deploy
|
|
|
|
|
command: |
|
|
|
|
|
git remote add storybook git@github.com:MetaMask/metamask-storybook.git
|
|
|
|
|
yarn storybook:deploy
|
|
|
|
|
|
|
|
|
|
test-unit:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: test:coverage
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
command: yarn test:coverage
|
|
|
|
|
- run:
|
|
|
|
|
name: test:coverage:jest
|
|
|
|
|
command: yarn test:coverage:jest
|
|
|
|
|
- persist_to_workspace:
|
|
|
|
|
root: .
|
|
|
|
|
paths:
|
|
|
|
|
- .nyc_output
|
|
|
|
|
- coverage
|
|
|
|
|
- jest-coverage
|
|
|
|
|
test-unit-global:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: test:unit:global
|
|
|
|
|
command: yarn test:unit:global
|
|
|
|
|
|
|
|
|
|
validate-source-maps:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: Validate source maps
|
|
|
|
|
command: yarn validate-source-maps
|
|
|
|
|
|
|
|
|
|
test-mozilla-lint:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- checkout
|
|
|
|
|
- attach_workspace:
|
|
|
|
|
at: .
|
|
|
|
|
- run:
|
|
|
|
|
name: test:mozilla-lint
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
5 years ago
|
|
|
command: NODE_OPTIONS=--max_old_space_size=3072 yarn mozilla-lint
|
|
|
|
|
|
|
|
|
|
all-tests-pass:
|
|
|
|
|
executor: node-browsers
|
|
|
|
|
steps:
|
|
|
|
|
- run:
|
|
|
|
|
name: All Tests Passed
|
|
|
|
|
command: echo 'weew - everything passed!'
|
