Integrate webext child pipeline
Background / User story
The "webext" child pipeline is expected to break when we switch over to the SDK (see #972 (closed)). Furthermore, most of the unit and end-to-end tests it includes are expected to be done by the SDK team. Therefore we should remove the child pipeline and run any remaining tasks as part of the main pipeline.
What to change
- Design: N/A
- Research: N/A
- Spec: N/A
- Legal: TBD
-
Development:
- Remove "webext" child pipeline:
- Remove the following CI jobs:
- audit
- docs
-
prepare-dependenciesmoved to #1002 (closed) - publish (see also adblockpluscore/.gitlab-pages.yml)
- Merge the following CI jobs into the main pipeline:
- build:chrome (see also #1002 (closed))
- build:firefox (see also #1002 (closed))
- build:source
- lint:js
- lint:yaml
- Remove the following tests:
- Extension loaded without errors
- CSS escaping unit tests
- Hostname extraction unit tests
-
testpages.adblockplus.org end-to-end tests (e.g. filter tests, subscription tests, subscribe URL tests)moved to #1002 (closed)
- (optional) Merge the following tests into the main pipeline:
- Preferences unit tests
- Uninstall URL unit tests
- Uninstall page opening end-to-end tests (see also #1002 (closed))
- Remove the following CI jobs:
- Remove "webext" child pipeline:
Hints for testers
- The "webext" child pipeline should be working again.
- The problem with adblockpluscore has been resolved (see #1012 (closed)).
- Builds failed to be generated due to missing dependencies.
- Generic "subscribe" testpages tests were skipped, causing an error to be thrown.
- Extension unit tests from the "webext" child pipeline are now running as part of our own end-to-end tests.
- Source archive files are now generated as part of the "build" and "build:with-snippets" CI jobs.
- YAML file linting is no longer of the CI pipeline, as it doesn't provide any additional value.
Hints for translators
N/A
Edited by Thomas Greiner