You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For building AMT, we use docker. As 'project base' we use a vendor image with Python pre-installed. This image is modified for the different purposes during build, like building the Python project, running tests and creating the production image.
The CI/CD creates the image each time 'from scratch', including an apt-get update and installing poetry, NVM and NodeJS.
This proces worked flawlessly, until we introduced NVM/NodeJS. For unknown reasons, downloading the required NodeJS package from the NodeJS website fails sometimes resulting in failing CI/CD.
Situation
For building AMT, we use docker. As 'project base' we use a vendor image with Python pre-installed. This image is modified for the different purposes during build, like building the Python project, running tests and creating the production image.
The CI/CD creates the image each time 'from scratch', including an apt-get update and installing poetry, NVM and NodeJS.
This proces worked flawlessly, until we introduced NVM/NodeJS. For unknown reasons, downloading the required NodeJS package from the NodeJS website fails sometimes resulting in failing CI/CD.
Solution
Split up the build for Python and NodeJS and use a different docker image for each step. This is however a bit complex, as our NPM webpack build generates javascript and stylesheets, but also creates jinja templates (from webpack templates). This means after this build, the results have to be copied to the next steps; but, that should be possible. There seems to be a NodeJS image: https://hub.docker.com/layers/library/node/20.16.0-bullseye-slim/images/sha256-69f4fc9de15e0a6315be58fa94d46f7cdc37fdf685d431727d1f49e4133ae6a0
The text was updated successfully, but these errors were encountered: