With Docker deployment, smaller images are usually better.
But your docker images will keep changing. And you just don’t remember to check it for a while. Then someday you happen to find out some huge images in your deployment pipeline. Feel uncomfortable, don’t you? Any thoughts about how to improve it?
My answer is like always: Monitor That! And Get Slack notifications.
Enclosed is my approach. Check it out! And discuss with me, my friends.
I use Jenkins quite a lot. Almost for everything in my daily work.
Not to mention CI/CD part. I achieve regular deployment from Jenkins. Daily backup and weekly cleanup from Jenkins. Vulnerability scan from Jenkins. Workflow enforcement from Jenkins. And the list goes on and on.
But just several years ago, Jenkins (Hudson, the old name) wasn’t this popular. And now? It is almost everywhere. Jenkins is just so important! So answer me: Why is that?
I think there are 5 reasons drive the changes. Check it out and share your thoughts with me, my friends!
(PS: check the bottom of the post: Top #10 Jenkins Plugins I’m actively using everyday).
Nowadays when people setup and configure services, probably nobody will enjoy doing it in a manual way.
Here comes a new question. How do you automate the process, and make it fast and reliable?
Wrap up some ssh scripts? Leverage CM(configuration management tools) like chef, ansible, or pupet? Use docker run? It’s great that we now have many options. But, as you may guess, not all of them are equally good.
You want a headache-free solution, right? And you also want it real quick, do you? Then You Can Not Miss docker-compose! Here are some useful tips and lessons learned using docker-compose.
Don’t make manual changes to the hosts file in your servers.
It would be hard to maintain. If you have to, here are 5 common issues I’d like you to know. And also some tips and free tools included in this post.
Check it out! And share it with your friends, if you find it useful.