Run Your CI in Code, Not YAML - Kyle Penfound, Dagger

Run Your CI in Code, Not YAML - Kyle Penfound, Dagger
`git commit -m 'fix ci'`. If you've made changes to a CI pipeline, you've probably committed a message like this many times. In this session I demonstrate a better way: CI pipelines as code. With years of experience in DevOps and Release Engineering, I've seen what makes CI hard. CI pipelines as code means writing CI logic with your preferred programming language instead of proprietary CI configuration yaml. Over time, CI configuration yaml grows longer and more complex. This makes it harder to read, test, and debug. CI pipelines as code solve this by bringing testability, readability - and even portability! This session will use real world examples to show how CI pipelines as code solves these problems and how you can implement pipelines as code today.

[@praveens2272]

No need to have code everywhere, sometimes simple and readable configuration like yml is enough. No need to complicate things with the code.

[@aromaticcut6898]

Yes bro yaml is easy to read and config

[@clintjedwards]

This is true until you're 40 levels deep in yaml inheritance hell and you wish instead of hacking together for loops from a configuration language that was never supposed to have one, you had just used the tooling and languages that you're already familiar with.

[@praveens2272]

@@clintjedwards I have not come across such complex level of yaml configuration.

[@valour.se47]

This tool is not for simple monoliths