The world of DevOps is incomplete without ‘Continuous Integration’ and ‘Continuous Deployment’ after all these are among the building blocks of the methodology. When we talk about CI/CD the first name that comes to most peoples’ notice is Jenkins, one of the oldest and most flourished CI/CD tool in existence, however, there is one more name that’s picking up the pace as we talk, Azure DevOps, formerly known as Team Foundation Server. In this blog, we will see a detailed comparison of these two players and which one is your best fit.Continue reading “Jenkins vs Azure DevOps”
Have you ever gone through the situation when your Jenkins goes down without any backup of your jobs and then you have to waste a lot of time and effort to re-create all your resources from scratch? We had also faced the same problem, but now We are free from it We have found a solution.
You might really want to know, how. What if, I say you can create a Jenkins server with the same configuration without any efforts and most importantly without wasting months, days, or even hours. Yes, you can set up your Jenkins in just 30 mins as we did.
So, basically what is Grandfather-father-son or GFS?
GFS backup is a common rotation scheme for backup, in which there are three or more backup cycles, such as daily, weekly, and monthly. Typically, It consists of daily backups (son, at fixed intervals of hours in a day), a weekly full backup (father, once a week), and monthly full backup (Grandfather, once a month).
While tools like Kubernetes is becoming an essential need for modern cloud-based infrastructure, there is a high potential for cloud-native CI/CD. To achieve that there is a philosophical approach has emerged i.e. GitOps. As we have discussed the important principles of GitOps in our previous blog, So in this blog, we will see how to implement GitOps in our current DevOps processes, and finally GitOps implementation in a light manner. If you haven’t gone through our previous blog, here you can take a look at it.
- Privately Hosted Jenkins
- Google developer console
Setup 1: Setup Ngrok
ngrok http 8080