Configuring a continuous integration pipeline
Not all languages are created equal, and while we could debate the benefits of strongly typed languages such as Java and Go versus untyped ones such as JavaScript, the fact is that we need to rely on unit tests to ensure that the code is working as intended. This is not a bad thing in itself—every code artifact should be supported by a set of tests with adequate coverage.
What does that have to do with a continuous delivery pipeline, you may be wondering? Well, it's all about the tests and, in the case of JavaScript code, this is very important. While pipeline will need to ensure the following:
- The code is meeting all quality rules
- All unit tests are successful
- All integration tests are successful
Once these steps are successful, then the process will be able to package and publish the result.
So, in the next sections, we will experiment with the deployment and configuration of our pipeline using one of the popular cloud-based continuous integration...
