CI/CD

Alright. This is the CI/CD corner of the knowledge base.

The ABC

I start from the basics. What a pipeline actually is. Jobs, stages, runners, artifacts. How you wire that into GitHub, GitLab, or Jenkins without copy-pasting someone else's YAML and hoping the green check means something.

Same ideas, different knobs

GitHub Actions, GitLab CI, Jenkins. I walk the platforms the way I'd explain them to another engineer. What I'd steal, what I'd skip, and where people usually get burned.

Then it gets serious

Then we get into the part that actually matters in production. Approvals. Secrets. Who can ship to prod. And enforcing SSDLC so security lives in the pipeline, not in a slide after the release.

A pipeline that only builds is half a pipeline

If it does not test, scan, and refuse a bad change, it is a deploy script with extra steps. That is the line we draw here.

Where to start

Need the version-control floor first? Go to Git. Then the platform pages. SSDLC sits on top once the basics are honest.