Unit testing of GitLab CI/CD pipelines themselves (like Jenkins Shared Pipeline Libraries Unit Tests)?

I am an experience Jenkins user and I am wondering if there is anything in GitLab analogous to Jenkins Pipeline Unit Testing capabilities?

How does one go about applying CI/CD best practices for GitLab ‘pipeline’ themselves? Or, how does gitlab facilitate ‘eating its own dog-food’ vis-a-vis CI/CD pipelines themselves.

Presumably, gitlab allows reuse of shared ‘code’ across multiple pipelines; so how are these to be themselves tested?

1 Like