We have a simple CI/CD pipeline which should build the Angular project and copy everything to another folder. The pipeline fails for no apparent reason.
Here’s our .gitlab-ci.yml
build_fe:
stage: build
only:
refs:
- dev
script:
- mkdir test
- cd Frontend
- npm i
- npm run build:test
- cp -r ./dist/projectname/* /var/www/test.domain.com/html
tags:
- test
And here are the logs (raw output):
Running with gitlab-runner 11.2.0 (11.2.0)
on TFCTestEnv V7-hsZQv
Using Shell executor...
msection_start:1620619532:prepare_script
Running on TFCTestEnv...
section_end:1620619532:prepare_script
section_start:1620619532:get_sources
Fetching changes...m
Removing Frontend/dist/
Removing Frontend/node_modules/
Removing test/
HEAD is now at c6c2c1e dev | updated ci/cd script
From https://gitlab.com/path
8ef5aba..f410014 updatedDependencies -> origin/updatedDependencies
Checking out c6c2c1e1 as dev...m
Skipping Git submodules setupm
section_end:1620619539:get_sources
section_start:1620619539:restore_cache
section_end:1620619539:restore_cache
section_start:1620619539:download_artifacts
section_end:1620619539:download_artifacts
section_start:1620619539:build_script
$ mkdir test
$ cd Frontend
$ npm i
added 1396 packages, and audited 1463 packages in 3m
63 vulnerabilities (63 low)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
$ npm run build:testm
> our-runner@0.0.0 build:test
> ng build --configuration=TFCTest
Browserslist: caniuse-lite is outdated. Please run next command `npm update`
When doing all of this manually on the machine it works flawlessly and IIRC it has worked in the past.
Does anyone know what’s going on?