←back to thread

Building a CI/CD Pipeline Runner from Scratch in Python

(muhammadraza.me)
55 points mr_o47 | 5 comments | 09 Nov 25 19:26 UTC | HN request time: 0.412s | source
Show context
systemerror ◴[12 Nov 25 17:52 UTC] No.45903306[source]▶
Why does air-gapped environment require rolling your own CI/CD solution? Plenty of examples of air-gapped Jenkins and/or Argo Workflows. Was this just an educational exercise?
replies(3): >>45904073 #>>45906749 #>>45906809 #
verdverm ◴[12 Nov 25 21:10 UTC] No.45906749[source]▶
Jenkins sucks but is insanely reliable

Argo Workflows does not live up to what they advertise, it is so much more complex to setup and then build workflows for. Helm + Argo is pain (both use the same template delimiters...)

replies(1): >>45907793 #
bigstrat2003 ◴[12 Nov 25 22:31 UTC] No.45907793[source]▶
Jenkins, like many tools with extreme flexibility, sucks as much as you make it suck. You can pretty easily turn Jenkins into a monstrosity that makes everyone afraid to ever try to update it. On the other hand, you can also have a pretty solid setup that is easy to work on. The trouble is that the tool itself doesn't guide you much to the good path, so unless you've seen a pleasant Jenkins instance before you're likely to have a worse time than necessary.
replies(1): >>45907969 #
1. IshKebab ◴[12 Nov 25 22:47 UTC] No.45907969[source]▶
Are you sure, because last time I used Jenkins it actively sucked. The interface was a total mess and it doesn't surface results in any useful way.
replies(2): >>45908393 #>>45908424 #
2. fowlie ◴[12 Nov 25 23:28 UTC] No.45908393[source]▶
When was the last time you used Jenkins? I don't get the hate. Not only from you, but lots of people on the internet. What makes Jenkins stand out IMO is the community and the core maintainers, they are perhaps moving slow, but they are moving in the right directions. The interface looks really nice now, they've done a lot of ux improvements lately.
replies(1): >>45908771 #
3. blackjack_ ◴[12 Nov 25 23:31 UTC] No.45908424[source]▶
What particular issues do you have with it? My company uses it at scale (dozens of different instances, hundreds of workers, thousands of pipelines) to support thousands of applications and we are reasonably happy with it. DSL is incredibly helpful at scale. IAC is incredibly helpful at scale. It requires a good amount of upkeep, but all things underpinning large amounts of infrastructure require a good amount of upkeep.
replies(1): >>45908837 #
4. verdverm ◴[13 Nov 25 00:15 UTC] No.45908771[source]▶
both the old & new interfaces to Jenkins are riddled with bugs, work seems to be maintenance mode, across the plugin ecosystem too

If you are talking about Jenkins-X, that is a different story, it's basically a rewrite to Kubernetes. I haven't talked to anyone actually using it, if you go k8s, you are far more likely to go argo

5. verdverm ◴[13 Nov 25 00:22 UTC] No.45908837[source]▶
We've minimized our usage of the DSL, there is no way for devs to debug it without pushing commits, and it means you have to implement much of your CI logic twice (once for local dev, once for ci system).

IMO, ci should be running the same commands humans would run (or could if it is production settings). Thus our Jenkins pipelines became a bunch of DSL boilerplate wrapped around make commands. The other nice thing about this is that it prepares you for easier migrations to a new ci system