As the number of our new (and old) customers grows, it becomes crucial to use IaC and enjoy all of its benefits like mitigation of human errors, infrastructure (self-)documentation etc. (more…)
As we’ve shared in our previous DevOps posts, we mainly use Jenkins for our common CI and CD tasks. Nowadays, Jenkins is still industry standard, there are heaps of resources tutorials and Stackoverflow threads about (almost) every conceivable issue. I’ve written “almost” back there, I know. Well, sometimes you have to dive in to Java code and figure out what the hell that XYZ plugin actually does. And things can get messy. But enough of complaints.
We have almost 50 developers working with different technologies to develop, test and ship apps for our demanding clients. With multiple git pushes and merge requests per hour there is a need for fast and optimized flow. Automating the CI/CD with multiple technologies and clouds/other deployment targets is critical for us. This is how we use powerful Jenkins Pipeline with Shared Pipeline Library with Jenkins and Gitlab.