TeamCity offers the ability to define project settings and configure CI/CD pipelines programmatically with the help of the Kotlin DSL.
To help you take advantage of the Kotlin DSL’s capabilities and simplify the build configuration process, we’ve created extensive Kotlin DSL documentation. It comes with examples that you can simply copy-paste directly into your code base.
Every TeamCity server has its own Kotlin DSL documentation, which is automatically curated to match the TeamCity version and any plugins installed on the server. If you install a new plugin, the documentation compiles again, providing you with relevant examples.
You can also refer to the general Kotlin DSL documentation, which is available in the TeamCity docs.
The Kotlin DSL documentation is available right from IntelliJ IDEA (both Ultimate and Community editions). You can access it by going to Maven Tool Window | Download Sources and Documentation.
Another way to access the Kotlin DSL documentation directly from your IDE is to run the
mvn -U dependency:sources command.
The documentation’s context and examples change when you click on an entity (for example, a build step or a trigger). The information is displayed either in a popup window or in the panel on the left, depending on the settings you’ve selected.
There are a few different ways to open the Kotlin DSL examples from your IDE:
F1on Mac or
Ctrl + Qon Windows. Refer to this section of the IntelliJ IDEA documentation for more details.
- Clicking on the name of an entity (such as a build step or a command). The examples will open in the menu on the right-hand side of the window.
- Simply hovering over an entity to access the in-line information window.
Using Kotlin DSL examples can save you time when configuring your pipelines as code. The examples also make it easier to discover all of the things you can do when configuring builds, in addition to helping you identify the scenarios that TeamCity can support.
Working with the Kotlin DSL examples can be a particularly great option when you are just getting started, as they provide a solid foundation on which to build your understanding of the Kotlin DSL.
TeamCity also provides you with an option to view your settings as code with the help of the View as code button, which is available on the build level. This displays your settings as code that you can copy and paste to your codebase.
If your project can’t be configured via the UI and you’d still like to experiment with the View as code feature, consider setting up a sandbox project on your TeamCity server. It will give you a chance to play around with different TeamCity features and see how they look in the Kotlin DSL.
If you’d like to learn more about using the Kotlin DSL for TeamCity, here are some additional resources that you might find useful:
- Video series “Kotlin DSL: From Zero to Hero”
- Blog post “Kotlin DSL for Beginners: Recommended Refactorings”
- Blog post “Creating TeamCity Project Templates with Kotlin DSL Context Parameters”
- Blog post series “Configuration as Code”
Do you have any questions or comments about how we can improve the Kotlin DSL examples and documentation for TeamCity? We’d love to get your feedback! Feel free to share it in the comment section below.