CICD is set up with CircleCI which uses docker containers to execute each step. The steps for the frontend are the equivalent of
- Continuous integration (CI)
docker run --rm --workdir /app -v (pwd)/frontend:/app --name tmp node yarn install
docker run --rm --workdir /app -v (pwd)/frontend:/app --name tmp node yarn test
docker run --rm --workdir /app -v (pwd)/frontend:/app --name tmp node yarn build
What this does is, it executes the three yarn (equivalent to npm) steps in an isolated container environment. What are containers? In short, the future of computing. It's not an overstatement, they are and will be everywhere. Google literally runs everything in containers.
- Continuous deployment (CD)
I configured the frontend to be deployed to a firebase hosting solution. For this I set up firebase-tools and added a firebase script to the package.json to avoid global installations. Next I did
yarn firebase init and
yarn firebase login:ci to get a token. This token is set in CircleCI as an environment variable (because it's a secret) and then used in the deploy step
The frontend (and hopefully also soon the backend) should be linted. Use this article for guidance