Until now, we did not pack the yarn packages installation in the docker image, because there was an issue with caching that we were not able to solve. Thanks to this advice, we can now move forward and put the necessary packages in the docker image, so that the actual yarn command be not any more run in the pipeline itself but in the dedicated docker image.
Until now, we did not pack the yarn packages installation in the docker image, because there was an issue with caching that we were not able to solve. Thanks to this advice, we can now move forward and put the necessary packages in the docker image, so that the actual
yarncommand be not any more run in the pipeline itself but in the dedicated docker image.