Jenkins pipelines as YAML
This is highly confusing to me. Pipelines in Jenkins are fragile. You can spend entire days trying to do <i>very</i> common things and run into tons of friction. The differences between scripted and declarative are severe, in terms of how erros and continuation are handled, the way that plugins interact depending on how you&#x27;ve nested stages and steps. Even things like environment vars and CWD can be a pain to coordinate. Trivial pipelines take far, far, far too long to setup and get working well.<p>This just appears to be a layer on top of the still-limited declarative pipelines. I&#x27;m not sure trading a groovy DSL for an extra layer (of yaml, no less) is a good deal.<p>It doesn&#x27;t solve the weirdness around multibranch, it doesn&#x27;t address the mismatch between having a parameterized pipeline where that parameterization has to live outside the Jenkinsfile (or if it is encoded in the Jenkinsfile, it acts really oddly, like running the Jenkinsfile actually reconfigures the job that invoked it, etc). This is why everyone has to continue using Groovy DSL and&#x2F;or JJB to reinstantiate parameterized jobs or handle jobs that deal with multiple Jenkinsfiles in a project.<p>I know Jenkins isn&#x27;t going anywhere but it&#x27;s legacy shows a lot.