Discussion on "Jenkins: The Ultimate Tool for Continuous Integration and Continuous Delivery (CI/CD)"

hello Chaitannyaa Gaikwad i am following your blog & trying to create this project Integration and Deployment (CI/CD) with Jenkins and ArgoCD can you help me currently i am facing this error

ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE this is another error that i got Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post

can you tell what credential did you add ec2 pem file? i tried adding the pem file content but it kept on still failing how do i resolve it

After a bad experience with Jenkins when I first started web development, I've actively avoided it. But reading through your article, it doesn't seem so bad now. It even looks nicer than I remember.

I'm glad that it was able to provide you with a more positive perspective on the tool. I would love to hear more about your past experiences with Jenkins and what made them negative.

Moreover, I am interested in applying my newly acquired knowledge of Jenkins to a practical project to further develop my skills. Could you suggest any project ideas that I could try out with Jenkins? I would greatly appreciate any guidance you can provide. Thank you in advance!

Chaitannyaa Gaikwad It was my second job, and after the main team left who managed Jenkins among other things (and who were exceptionally more senior and advanced than I was), I found it incredibly complex to use as a beginner developer versus something like TravisCI or now GitHub Actions. Because of this complexity, I opted for simpler and easier solutions ever since.

First off, in my first few years of development, I wasn't smart as you to take the time to learn Jenkins. But your tutorial has made me want to revisit it again. So I'm sure I'd be learning from you!

If I were to use it again, I'd use it to split my CI from CD solution. So I'd continue with GitHub Actions for CI to build an artifact, like a containerized image or zip. Then I'd use Jenkins for CD, allowing non-engineering to trigger deployments and move releases through a QA->UAT->pre-prod->production pipeline using a nice GUI interface. I know this can be achieved through GitHub Actions (especially their higher-tiered versions), but with cost-savings, Jenkins now looks like a good solution.

Thank you Gemma Black for sharing your experience with Jenkins and your perspective on using it for CI/CD. It's great to hear that my tutorial has inspired you to revisit it again.

Splitting CI/CD solution and using GitHub Actions for CI and Jenkins for CD that sounds like an interesting approach to me. It's always good to explore new ways of doing things and see what works best for our particular use case.

Thank you so much for taking the time to give me such an elaborate response and I will definitely consider using your suggestion as I move forward with my project.Thanks again!

Search Hashnode

Jenkins: The Ultimate Tool for Continuous Integration and Continuous Delivery (CI/CD)

Responses(2)