I will see
As a counter example for this shitty solution: 1. Bad developer injects some custom script into the "build" script of "package.json" 2. Runner runs the trusted "npm run build" command 3. Everything goes down
you're supposed to have a quality gate
So, you need to have quality gate for the entire source code, which developer may inject some code and they will run automatically
ok, look, you're a talker. And since you like to talk rather than understand the matter, I recommend to write a blogpost where you explain gitlab or any saas that what they got is wrong, and they should do things differently. And you add all your nonsense wall of text. Maybe someone can school you better on this basic concepts
Why don't you search a little ?? Why not talk to credible evidence from credible sources? This project is Gitlab itself Look at it carefully Because you will see all the CI files inside Because they do not need to be hide They only run by domain https://gitlab.com/gitlab-org/gitlab/-/tree/master/.gitlab/ci
Обсуждают сегодня