4 ms·
The yaml config is perfectly suited for small/toy projects, which is probably what GitHub intended. Even in larger projects I've never had to use the scripting
by momothereal 6y ago
The yaml config is perfectly suited for small/toy projects, which is probably what GitHub intended. Even in larger projects I've never had to use the scripting language.
On the other end, we now use Jenkins (the newer version), so every job is a huge Groovy script pretending to be a config file. Much steeper learning curve for anything simple.
Pick your poison.
- baq 6y agoi'm in an apparent minority that thinks configuration shouldn't be turing-complete :) but then, to counter my own point, 'configuration' is not as easy to define as i'd like.
- deleted 6y ago[deleted]
- toomanybeersies 6y agoI feel like ruby (or a DSL written in ruby) would be the ideal language for writing CI pipeline "configurations". You'd end up with config files that are actually readable (even to non-rubyists), with a shallow learning curve, but still easily extensible. Here's a 5 minute mockup: https://gist.github.com/gkampjes/559ebe708343bb7c2f590c0065d943a9 https://gist.github.com/gkampjes/559ebe708343bb7c2f590c0065d... Looks nicer than any .yaml file (or Groovy script) I've ever seen.