Jenkins core is undergoing huge product and user experience refactoring. By introducing pipeline-as-code, that is based on Groovy, Jenkins team and community is moving towards having continuous delivery pipelines as first-class citizens inside Jenkins. This transformation is not going as smooth as it could, but it is going forward. The author will try to show some common pitfalls, shortcuts, and tricks for defining your pipelines with the help of Groovy as well as how to write your own pipeline step libraries.