To understand what is DevOps first you need to learn about its life cycle. Our task is to automate the entire process, from the development process to the time we get it into production. That’s the time when we need Continuous Integration/Continuous Deployment skills. Let’s present you the CI/CD pipeline using Docker and Jenkins. Step by step.
Last time we talked about the pros and cons of DevOps as a Service. There we mentioned AWS and Google Cloud Platform as the main platforms that are frequently used by DevOps. Why can’t we make a small comparison for them? Sure, there’s also Microsoft Azure among the giants. But we’ll come back to it later. So, today we have AWS vs Google Cloud Platform. What is better for DevOps in the cloud?
Cool tools time! Our article about continuous integration and delivery with Github, Gitflow, and Jenkins that presented you the step-by-step guide with the set of rules for development. Today we’d like to share with you the new CI/CD solution, Jenkins X for cloud applications on Kubernetes.
This article is related to our material about continuous integration and delivery with Github, Gitflow, and Jenkins. But this time we will expand the topic of continuous integration with Jenkins and dive into details about Jenkins Pipelines. Here you will find everything you wanted to know about continuous integration with Jenkins Pipeline!
Today is Monday evening (October the 3d). Warm and fuzzy to deliver our digest. Rschema a good article, which present immutable goodness of having type constrained record-like objects in Ruby. Really pleasant to read. Hamster gem which will help to build your code with fuzzy immutable objects. Are you ready for ruby 3.x? Tme based estimates won’t get…
Collection of rules for development, continuous integration, QA and deploy with Github, Gitflow, and Jenkins we use in one project with 5 teams distributed across 4 locations and developing Ruby on Rails backend for native mobile apps. Syndicode created step-by-step guide below.