We have begun to leverage Docker for building our Node.js middleware applications and front end code. This originally came out of necessity since we had some repositories dependent on version 4 of Node and others on 6, but only 4 installed on the Jenkins agents. Rather than install both versions of Node and toggle them using a node version manager like n or, worse yet, using Jenkins tags to have some agents with one version and some with the other, we decided instead to try using Docker to manage the version of Node. Read more click here
We have begun to leverage Docker for building our Node.js middleware applications and front end code. This originally came out of necessity since we had some repositories dependent on version 4 of Node and others on 6, but only 4 installed on the Jenkins agents. Rather than install both versions of Node and toggle them using a node version manager like n or, worse yet, using Jenkins tags to have some agents with one version and some with the other, we decided instead to try using Docker to manage the version of Node. Read more click here

This blog gives a very clear and helpful introduction to using Docker for continuous delivery. I appreciate how it explains the basics in simple language, especially for someone who is new to containers and DevOps practices. Learning how Docker helps package applications and make deployments more consistent really shows why it’s become such an important tool in modern software teams. The post also makes it easy to understand how Docker fits into the delivery pipeline and improves automation, speed, and reliability. Overall, this article is a great starting point for anyone wanting to learn how containers and continuous delivery work together. It’s practical, easy to follow, and very useful for both beginners and learners who want to build real DevOps skills.
ReplyDelete