Imagine you have just switched your TeamCity project over to Kotlin DSL. Your builds run successfully, but what next? What small refactorings can you apply to your Kotlin DSL code to help keep it clean and tidy?
In this article, we'll discuss the next steps you can take.
1. Remove disabled build steps, triggers & requirements
If you used the UI before switching to Kotlin DSL, there is a significant chance your build scripts contain a fair number of disabled settings, like obsolete build steps, triggers, and requirements.
Instead of keeping those settings in your build scripts, let's simp