2021-10-18 13:05:25 +03:00
|
|
|
version: 2.1
|
2018-04-20 14:46:08 +03:00
|
|
|
|
2021-10-18 13:05:25 +03:00
|
|
|
orbs:
|
2022-12-15 19:13:13 +02:00
|
|
|
ruby: circleci/ruby@2.0.0
|
|
|
|
node: circleci/node@5.0.3
|
2021-10-18 13:05:25 +03:00
|
|
|
|
|
|
|
executors:
|
|
|
|
default:
|
|
|
|
parameters:
|
|
|
|
ruby-version:
|
|
|
|
type: string
|
2018-04-20 14:46:08 +03:00
|
|
|
docker:
|
2021-10-18 13:05:25 +03:00
|
|
|
- image: cimg/ruby:<< parameters.ruby-version >>
|
|
|
|
environment:
|
2020-05-01 21:19:01 +03:00
|
|
|
BUNDLE_JOBS: 3
|
|
|
|
BUNDLE_RETRY: 3
|
2021-10-18 13:05:25 +03:00
|
|
|
CONTINUOUS_INTEGRATION: true
|
2018-04-20 14:46:08 +03:00
|
|
|
DB_HOST: localhost
|
|
|
|
DB_USER: root
|
2018-05-09 17:59:58 +03:00
|
|
|
DISABLE_SIMPLECOV: true
|
2021-10-18 13:05:25 +03:00
|
|
|
RAILS_ENV: test
|
2022-12-15 19:13:13 +02:00
|
|
|
- image: cimg/postgres:14.5
|
2021-10-18 13:05:25 +03:00
|
|
|
environment:
|
|
|
|
POSTGRES_USER: root
|
|
|
|
POSTGRES_HOST_AUTH_METHOD: trust
|
2022-12-15 19:13:13 +02:00
|
|
|
- image: cimg/redis:7.0
|
2018-04-23 10:16:26 +03:00
|
|
|
|
2021-10-18 13:05:25 +03:00
|
|
|
commands:
|
|
|
|
install-system-dependencies:
|
2018-04-20 14:46:08 +03:00
|
|
|
steps:
|
2020-05-01 21:19:01 +03:00
|
|
|
- run:
|
2021-10-18 13:05:25 +03:00
|
|
|
name: Install system dependencies
|
|
|
|
command: |
|
|
|
|
sudo apt-get update
|
2022-02-14 17:08:02 +02:00
|
|
|
sudo apt-get install -y libicu-dev libidn11-dev
|
2021-10-18 13:05:25 +03:00
|
|
|
install-ruby-dependencies:
|
|
|
|
parameters:
|
|
|
|
ruby-version:
|
|
|
|
type: string
|
|
|
|
steps:
|
|
|
|
- run:
|
|
|
|
command: |
|
|
|
|
bundle config clean 'true'
|
|
|
|
bundle config frozen 'true'
|
|
|
|
bundle config without 'development production'
|
|
|
|
name: Set bundler settings
|
|
|
|
- ruby/install-deps:
|
2022-12-15 19:13:13 +02:00
|
|
|
bundler-version: '2.3.26'
|
2021-10-18 13:05:25 +03:00
|
|
|
key: ruby<< parameters.ruby-version >>-gems-v1
|
|
|
|
wait-db:
|
|
|
|
steps:
|
|
|
|
- run:
|
|
|
|
command: dockerize -wait tcp://localhost:5432 -wait tcp://localhost:6379 -timeout 1m
|
|
|
|
name: Wait for PostgreSQL and Redis
|
2018-04-20 14:46:08 +03:00
|
|
|
|
|
|
|
jobs:
|
2018-04-23 10:16:26 +03:00
|
|
|
build:
|
2021-10-18 13:05:25 +03:00
|
|
|
docker:
|
2021-11-18 22:59:57 +02:00
|
|
|
- image: cimg/ruby:3.0-node
|
2021-10-18 13:05:25 +03:00
|
|
|
environment:
|
|
|
|
RAILS_ENV: test
|
2018-04-23 10:16:26 +03:00
|
|
|
steps:
|
2021-10-18 13:05:25 +03:00
|
|
|
- checkout
|
|
|
|
- install-system-dependencies
|
|
|
|
- install-ruby-dependencies:
|
2021-11-18 22:59:57 +02:00
|
|
|
ruby-version: '3.0'
|
2021-10-18 13:05:25 +03:00
|
|
|
- node/install-packages:
|
|
|
|
cache-version: v1
|
|
|
|
pkg-manager: yarn
|
2020-05-01 21:19:01 +03:00
|
|
|
- run:
|
2022-11-30 10:56:27 +02:00
|
|
|
command: |
|
|
|
|
export NODE_OPTIONS=--openssl-legacy-provider
|
|
|
|
./bin/rails assets:precompile
|
2021-10-18 13:05:25 +03:00
|
|
|
name: Precompile assets
|
2018-07-30 23:22:55 +03:00
|
|
|
- persist_to_workspace:
|
2018-04-23 10:16:26 +03:00
|
|
|
paths:
|
2021-10-18 13:05:25 +03:00
|
|
|
- public/assets
|
|
|
|
- public/packs-test
|
|
|
|
root: .
|
|
|
|
|
|
|
|
test:
|
|
|
|
parameters:
|
|
|
|
ruby-version:
|
|
|
|
type: string
|
|
|
|
executor:
|
|
|
|
name: default
|
|
|
|
ruby-version: << parameters.ruby-version >>
|
|
|
|
environment:
|
|
|
|
ALLOW_NOPAM: true
|
|
|
|
PAM_ENABLED: true
|
|
|
|
PAM_DEFAULT_SERVICE: pam_test
|
|
|
|
PAM_CONTROLLED_SERVICE: pam_test_controlled
|
|
|
|
parallelism: 4
|
|
|
|
steps:
|
|
|
|
- checkout
|
|
|
|
- install-system-dependencies
|
|
|
|
- run:
|
|
|
|
command: sudo apt-get install -y ffmpeg imagemagick libpam-dev
|
|
|
|
name: Install additional system dependencies
|
|
|
|
- run:
|
|
|
|
command: bundle config with 'pam_authentication'
|
|
|
|
name: Enable PAM authentication
|
|
|
|
- install-ruby-dependencies:
|
|
|
|
ruby-version: << parameters.ruby-version >>
|
|
|
|
- attach_workspace:
|
|
|
|
at: .
|
|
|
|
- wait-db
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:create db:schema:load db:seed
|
|
|
|
name: Load database schema
|
|
|
|
- ruby/rspec-test
|
2018-04-23 10:16:26 +03:00
|
|
|
|
2020-01-11 03:04:57 +02:00
|
|
|
test-migrations:
|
2021-10-18 13:05:25 +03:00
|
|
|
executor:
|
|
|
|
name: default
|
2021-11-18 22:59:57 +02:00
|
|
|
ruby-version: '3.0'
|
2020-01-11 03:04:57 +02:00
|
|
|
steps:
|
2021-10-18 13:05:25 +03:00
|
|
|
- checkout
|
|
|
|
- install-system-dependencies
|
|
|
|
- install-ruby-dependencies:
|
2021-11-18 22:59:57 +02:00
|
|
|
ruby-version: '3.0'
|
2021-10-18 13:05:25 +03:00
|
|
|
- wait-db
|
2020-01-11 03:04:57 +02:00
|
|
|
- run:
|
2020-05-01 21:19:01 +03:00
|
|
|
command: ./bin/rails db:create
|
2021-10-18 13:05:25 +03:00
|
|
|
name: Create database
|
2022-01-31 00:50:08 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20171010025614
|
|
|
|
name: Run migrations up to v2.0.0
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2
|
|
|
|
name: Populate database with test data
|
2022-03-08 00:40:55 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20180514140000
|
|
|
|
name: Run migrations up to v2.4.0
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2_4
|
|
|
|
name: Populate database with test data
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20180707154237
|
|
|
|
name: Run migrations up to v2.4.3
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2_4_3
|
|
|
|
name: Populate database with test data
|
2020-01-11 03:04:57 +02:00
|
|
|
- run:
|
2020-05-01 21:19:01 +03:00
|
|
|
command: ./bin/rails db:migrate
|
2022-01-31 00:50:08 +02:00
|
|
|
name: Run all remaining migrations
|
2022-03-08 00:40:55 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:check_database
|
|
|
|
name: Check migration result
|
2022-01-31 00:50:08 +02:00
|
|
|
|
|
|
|
test-two-step-migrations:
|
|
|
|
executor:
|
|
|
|
name: default
|
|
|
|
ruby-version: '3.0'
|
|
|
|
steps:
|
|
|
|
- checkout
|
|
|
|
- install-system-dependencies
|
|
|
|
- install-ruby-dependencies:
|
|
|
|
ruby-version: '3.0'
|
|
|
|
- wait-db
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:create
|
|
|
|
name: Create database
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20171010025614
|
|
|
|
name: Run migrations up to v2.0.0
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2
|
|
|
|
name: Populate database with test data
|
2022-03-08 00:40:55 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20180514140000
|
|
|
|
name: Run pre-deployment migrations up to v2.4.0
|
|
|
|
environment:
|
|
|
|
SKIP_POST_DEPLOYMENT_MIGRATIONS: true
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2_4
|
|
|
|
name: Populate database with test data
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate VERSION=20180707154237
|
|
|
|
name: Run migrations up to v2.4.3
|
|
|
|
environment:
|
|
|
|
SKIP_POST_DEPLOYMENT_MIGRATIONS: true
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:populate_v2_4_3
|
|
|
|
name: Populate database with test data
|
2022-01-31 00:50:08 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
name: Run all remaining pre-deployment migrations
|
2022-03-06 23:51:40 +02:00
|
|
|
environment:
|
2022-01-31 00:50:08 +02:00
|
|
|
SKIP_POST_DEPLOYMENT_MIGRATIONS: true
|
|
|
|
- run:
|
|
|
|
command: ./bin/rails db:migrate
|
Revamp post filtering system (#18058)
* Add model for custom filter keywords
* Use CustomFilterKeyword internally
Does not change the API
* Fix /filters/edit and /filters/new
* Add migration tests
* Remove whole_word column from custom_filters (covered by custom_filter_keywords)
* Redesign /filters
Instead of a list, present a card that displays more information and handles
multiple keywords per filter.
* Redesign /filters/new and /filters/edit to add and remove keywords
This adds a new gem dependency: cocoon, as well as a npm dependency:
cocoon-js-vanilla. Those are used to easily populate and remove form fields
from the user interface when manipulating multiple keyword filters at once.
* Add /api/v2/filters to edit filter with multiple keywords
Entities:
- `Filter`: `id`, `title`, `filter_action` (either `hide` or `warn`), `context`
`keywords`
- `FilterKeyword`: `id`, `keyword`, `whole_word`
API endpoits:
- `GET /api/v2/filters` to list filters (including keywords)
- `POST /api/v2/filters` to create a new filter
`keywords_attributes` can also be passed to create keywords in one request
- `GET /api/v2/filters/:id` to read a particular filter
- `PUT /api/v2/filters/:id` to update a new filter
`keywords_attributes` can also be passed to edit, delete or add keywords in
one request
- `DELETE /api/v2/filters/:id` to delete a particular filter
- `GET /api/v2/filters/:id/keywords` to list keywords for a filter
- `POST /api/v2/filters/:filter_id/keywords/:id` to add a new keyword to a
filter
- `GET /api/v2/filter_keywords/:id` to read a particular keyword
- `PUT /api/v2/filter_keywords/:id` to edit a particular keyword
- `DELETE /api/v2/filter_keywords/:id` to delete a particular keyword
* Change from `irreversible` boolean to `action` enum
* Remove irrelevent `irreversible_must_be_within_context` check
* Fix /filters/new and /filters/edit with update for filter_action
* Fix Rubocop/Codeclimate complaining about task names
* Refactor FeedManager#phrase_filtered?
This moves regexp building and filter caching to the `CustomFilter` class.
This does not change the functional behavior yet, but this changes how the
cache is built, doing per-custom_filter regexps so that filters can be matched
independently, while still offering caching.
* Perform server-side filtering and output result in REST API
* Fix numerous filters_changed events being sent when editing multiple keywords at once
* Add some tests
* Use the new API in the WebUI
- use client-side logic for filters we have fetched rules for.
This is so that filter changes can be retroactively applied without
reloading the UI.
- use server-side logic for filters we haven't fetched rules for yet
(e.g. network error, or initial timeline loading)
* Minor optimizations and refactoring
* Perform server-side filtering on the streaming server
* Change the wording of filter action labels
* Fix issues pointed out by linter
* Change design of “Show anyway” link in accordence to review comments
* Drop “irreversible” filtering behavior
* Move /api/v2/filter_keywords to /api/v1/filters/keywords
* Rename `filter_results` attribute to `filtered`
* Rename REST::LegacyFilterSerializer to REST::V1::FilterSerializer
* Fix systemChannelId value in streaming server
* Simplify code by removing client-side filtering code
The simplifcation comes at a cost though: filters aren't retroactively
applied anymore.
2022-06-28 10:42:13 +03:00
|
|
|
name: Run all post-deployment migrations
|
2022-03-08 00:40:55 +02:00
|
|
|
- run:
|
|
|
|
command: ./bin/rails tests:migrations:check_database
|
|
|
|
name: Check migration result
|
2018-04-20 14:46:08 +03:00
|
|
|
|
|
|
|
workflows:
|
|
|
|
version: 2
|
|
|
|
build-and-test:
|
|
|
|
jobs:
|
2021-10-18 13:05:25 +03:00
|
|
|
- build
|
|
|
|
- test:
|
|
|
|
matrix:
|
|
|
|
parameters:
|
|
|
|
ruby-version:
|
|
|
|
- '2.7'
|
|
|
|
- '3.0'
|
|
|
|
name: test-ruby<< matrix.ruby-version >>
|
2021-05-06 15:22:54 +03:00
|
|
|
requires:
|
2020-01-10 06:34:25 +02:00
|
|
|
- build
|
2021-10-18 13:05:25 +03:00
|
|
|
- test-migrations:
|
2018-12-29 08:23:07 +02:00
|
|
|
requires:
|
|
|
|
- build
|
2022-01-31 00:50:08 +02:00
|
|
|
- test-two-step-migrations:
|
|
|
|
requires:
|
|
|
|
- build
|
2021-10-18 13:05:25 +03:00
|
|
|
- node/run:
|
|
|
|
cache-version: v1
|
|
|
|
name: test-webui
|
|
|
|
pkg-manager: yarn
|
2021-05-06 15:22:54 +03:00
|
|
|
requires:
|
|
|
|
- build
|
2022-12-15 18:43:26 +02:00
|
|
|
version: '16.18'
|
2021-10-18 13:05:25 +03:00
|
|
|
yarn-run: test:jest
|