Building a CI/CD Pipeline Runner from Scratch in Python

(muhammadraza.me)
29 points mr_o47 | 9 comments | 09 Nov 25 19:26 UTC | HN request time: 1.041s | source | bottom
1. 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 #
2. mr_o47 ◴[12 Nov 25 18:41 UTC] No.45904073[source]▶
This was more like an educational exercise
replies(1): >>45904136 #
3. esafak ◴[12 Nov 25 18:45 UTC] No.45904136{3}[source]▶
Since you're exercising, you can take it to the next level where you don't specify the next step but the inputs to each task, allowing you to infer the DAG and implement caching...
replies(1): >>45906728 #
4. ◴[12 Nov 25 20:30 UTC] No.45906116[source]▶
5. verdverm ◴[12 Nov 25 21:09 UTC] No.45906728{4}[source]▶
You can do this with cue/flow, but have not turned it into a full CI system. The building blocks are there
replies(1): >>45907355 #
6. 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...)

7. piker ◴[12 Nov 25 21:14 UTC] No.45906809[source]▶
It seems like a simple CI/CD in an airgapped environment might be simpler to implement than to (1) learn and (2) onboard an off-the-shelf solution when your airgapped requirement limits your ability to leverage the off-the-shelf ecosystem.
8. mr_o47 ◴[12 Nov 25 21:57 UTC] No.45907355{5}[source]▶
Never heard of cue/flow will definitely check it out