GitLab CI/CD Compliance

Posted by diviNeCall on Monday February 23, 2026 @08:06AM
from the github.com dept.

( 3 comments | 3 points | on HN )

Re:GitLab CI/CD Compliance by diviNeCall on Monday February 23, 2026 @08:06AM (#47121810)

I’m explicitly looking for people to tear this apart: if you assume a hostile developer who controls .gitlab-ci.yml but not the platform, can you design a CI/CD compliance model on GitLab that actually can’t be bypassed. And if you think you can, please explain how, and if you think it’s impossible, I want to hear that too.

[ Parent | on HN ]

Re:GitLab CI/CD Compliance by diviNeCall on Monday February 23, 2026 @08:07AM (#47121831)

I want to know if my CLI actually helps or if it misses the point of supply-chain defense and compliance.

[ Parent | on HN ]

Re:GitLab CI/CD Compliance by brudgers on Monday February 23, 2026 @05:08PM (#47129686)

If it meets the guidelines, this might make a good 'Show HN'. Show HN guidelines: https://news.ycombinator.com/showhn.html

[ Parent | on HN ]