News for hackers. Stuff that matters.

A comment on Why We’re Sticking with Ruby on Rails at Gitlab. Parent comment

Re:Why We’re Sticking with Ruby on Rails at Gitlab by jmholla on Monday June 13, 2022 @03:34PM (#31730569)
> Also, it would be nice if their CI/CD could be defined in multiple .yml instead of one giant file that I seem to end up in most projects.

It can. You can use `include` to include templates and job definitions from other files. Also, with child pipelines (i.e. trigger jobs), you can run a pipeline defined in a separate YAML file.

[ Parent | on HN ]
Re:Why We’re Sticking with Ruby on Rails at Gitlab by safaci2000 on Monday June 13, 2022 @03:56PM (#31730919)
sure, I've touched on include a bit and removes some of the repetitive code.

I would rather have something like:

release.yml documentation.yml security-scan.yml

I know you can define all these in a common repo and then have a few lines to include them but it's not exactly the same IMO.

Not to mention that now I need to pull another repo to see what is going on and why the task no longer works.

[ Parent | on HN ]