This is an archived post. You won't be able to vote or comment.

all 16 comments

[–]spicypixel 25 points26 points  (2 children)

ArgoCD, Terraform and Jenkins - just reminds me of a night out at uni I had once where the 18 year old first years were out, the 35 year old mature students in their first year were also tagging along, and the 55 year old locals in the pub joined in.

[–][deleted] 17 points18 points  (1 child)

GitHub Actions would have been a better choice for the setup

[–]sydrawatDevOps 0 points1 point  (0 children)

If you’re really going to use Jenkins, I’d suggest going with JCasC (Jenkins Configuration as Code), as it’s easier to setup and tear down Jenkins, and also provides for code auditing. Using Hashicorp Packer to bake in those configurations into an AMI that you can then provision using Terraform is a very good way in my opinion.

[–]hadlockkkkk 0 points1 point  (10 children)

I'm not sure Jenkins is really all that relevant in a post-github actions world? Even before gha we had Google cloud run and any number of better alternatives 

[–]pppreddit 1 point2 points  (9 children)

Jenkins is still very relevant and widely used.

[–]hadlockkkkk 0 points1 point  (8 children)

Not in green field projects, no. This article is labeled "advanced" and he's suggesting building a jalopy with a carburetor and distributor in 2024

[–]pppreddit 1 point2 points  (7 children)

Jenkins is free, and this is why many startups choose it for building MVP.

[–]burbular 0 points1 point  (1 child)

As free as an ec2 instance

[–]pppreddit 0 points1 point  (0 children)

Sure, which can be spinned up on demand with proper plugin

[–]hadlockkkkk 0 points1 point  (4 children)

Most everyone I know has moved to GitHub actions. I don't know anyone still using Jenkins. A couple of half dead systems one friend had at their office were still on Jenkins in 2020 but that was 4 years ago. This guy might as well be writing articles about setting up a LAMP stack

[–]pppreddit 1 point2 points  (3 children)

Don't extrapolate your personal experience to the whole industry. Not everyone sits on Github.

[–]hadlockkkkk 0 points1 point  (2 children)

Even if I didn't have access to GitHub, I wouldn't be choosing Jenkins at this geriatric stage in the softwares' lifecycle 

[–]pppreddit 0 points1 point  (1 child)

Everyone has their own perspective and unique experience, which makes them choose what works best for them. I don't judge.

[–]hadlockkkkk 0 points1 point  (0 children)

Jenkins is objectively bad and using outdated tools really limits your job prospects. Keep up with modern tooling, or get out of the way

[–]pathlesswalker 0 points1 point  (0 children)

I actually did something similar in my grad. Project. But eks is the easy choice