Implement caching of NPM in CI / local dev #43167
Labels
area:CI
Airflow's tests and continious integration
area:dev-env
CI, pre-commit, pylint and other changes that do not change the behavior of the final code
Currently when NPM packages are installed on CI they are installed from the scratch by "compile www assets" pre-commit.
This causes fairly frequent, intermittent issues when there is a networking issue or NPM server issue - for example:
We should - similarly to Python packages, implement caching strategy that should speed up the installation of npm packages on a clean CI runner, as well as local development instance - where previously installed packages could be stored in the cache and reused. This should increase both - speed of CI jobs an stability of them (and speed of local installation of npm packages).
The text was updated successfully, but these errors were encountered: