Too many concepts, new words, and tools in DevOps world.
Here I try to dig deeper for some interesting facts.
You have more puzzles or related knowledge? Please share with me by adding comments.
Attentions, Chef Users. I’ve exported my Chef experience to GitHub.
No overwhelming info. Less frustration. It starts with real and specific requirements. From easy to difficult, step-by-step.
You need to hire Chef candidates? Apply Chef jobs? Or simply sharpen your Chef skills at work?
Take five minutes and check it out now: chef-study.
Please let me know what you think. Thus I can better help you and your case.
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).
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.