I recently discovered
npm ci which you can use instead of
npm install when running a node project on continuous integration (CI) system and want to install your npm dependencies. It does this in a more lightweight, more CI friendly way.
If you use
npm test to run your tests, this can be shortened to
npm t (much like
npm i is
npm install), and therefore you can run
npm cit to install dependencies and run tests in CI.
Manoj Kumar K asked me via LinkedIn for some feedback on his article about the differences between Continuous Integration/Testing/Delivery and Deployment.
Here’s my response (left as a comment on the original article):
Continuous Integration is continually integrating several developer’s code, compiling, deploying and automatically testing that code (Continuous Testing), and that can be done on a branch, or in trunk/master.
When you have continual production readiness of every build, but you don’t deploy every build automatically, instead you choose to deploy say x times a week, that is Continuous Delivery.
When you automatically deploy every build to production after it’s been automatically integrated, built and tested, that is Continuous Deployment.
I’ve previously briefly explained the semantics here.
So Continuous Integration (CI) and Continuous Testing together allow Continuous Delivery. Continuous Delivery allows Continuous Deployment (should you choose to do this).
Martin Fowler explains this in more detail here.
If your development machines don’t have solid state drives (SSDs): go buy some.
If your continous integration (build) box doesn’t have a solid state drive: go buy one.
Solid state drives are the quickest and cheapest way to speed software development. As most continuous integrations/builds are IO, solid state drives provide tremendous speed increases: I’ve seen builds and tests run in less than a fifth of the time a traditional moving hard disk would take. Solid state drives have reached a price point where the lower capacity ones are on par with higher capacity hard disks (which you don’t need unless you’re storing movies etc.)
It used to be that the build machine would use some crappy hardware lying around: often an old development machine someone no longer used. This is one of the worst decisions you can make on a project.
Having a super fast SSD based build machine will ensure fast, reliable build results, fast feedback and a happy development team.