I was wondering if there is a way to validate a .gitlab-ci.yml file more robustly than just linting it. I want to verify the behavior of the
rules that I’ve added (because frankly the behavior of rules is confusing and often unintuitive) without actually running the pipeline.
I have some hidden jobs that are extended by various other jobs in the pipeline, and I want to ensure that the right jobs are triggered in the right scenarios (based on changes to files in certain folders, some also based on the current ref, some based on variables).
What I’m looking for is something along the lines of
helm template where you can set parameters and evaluate the output locally to ensure a chart’s logic is correct.
I can’t find anything in the documentation that suggests this is possible. I was wondering if anyone has any tricks they’ve come up with themselves?