Beyond CI/CD: GitLab's DevOps Vision (2017)

Re:Beyond CI/CD: GitLab's DevOps Vision (2017) by Already__Taken on Monday March 19, 2018 @06:12AM (#16617275)

Can't you put the gitlab runner on whatever you want and set up CI environments to the runner?

[ Parent | on HN ]

Re:Beyond CI/CD: GitLab's DevOps Vision (2017) by bpicolo on Monday March 19, 2018 @08:20AM (#16617804)

The issue is that the configuration format makes complex jobs difficult to define. It's good for the simple case, but versus e.g. a Jenkinsfile[0] where you get a complete groovy DSL that can interact with it's environment across tasks, pipeline, branch, etc with ease it's rough. Having fine-grained control becomes important.

[0] https://jenkins.io/doc/book/pipeline/jenkinsfile/

[ Parent | on HN ]

Re:Beyond CI/CD: GitLab's DevOps Vision (2017) by vorg on Monday March 19, 2018 @06:18PM (#16623790)

> a Jenkinsfile[0] where you get a complete groovy DSL

Apache Groovy isn't "complete" as shipped with Jenkins. It's collections API is deliberately crippled so it doesn't work.

[ Parent | on HN ]