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).
Following git workflows, there is a branch called activesprint, or develop. It is the release candidate. Most of active branches should base on it.
Team need to be notified, whenever a new activesprint branch has been created. To lower the communication effort, we can automate the detection process and get slack notifications.
Has the deployment been initiated? Already finished? And how does it look after the deployment? These are typical questions people will frequently ask. Especially managers and key holders.
Thanks to Slack, team can sync up much easier than before. With more and more DevOps adoptions, we’re likely to have one-button click deployment.
Let’s send out slack notifications for system upgrade. Better sync up, better control.
After a lot of effort and communication, finally the system deployment works! To guarantee a smooth deployment anytime, we enforce daily deployment test as a next step.
Surprisingly daily deployment doesn’t always succeed like we expect, even if no major changes. More interesting, many failed tests are kinds of false negatives. So what are the obstacles? And how we can avoid them?