What are the implications of changing versioned settings from xml to kotlin?
Completed
We have an existing settings repo (10k plus commits) configured with xml. What impact will see in the Ui if we just change the format to kotlin?
Please sign in to leave a comment.
Hello, nothing should change in the UI.
When you change Versioned settings format from XML to Kotlin, you can tick the "Generate portable DSL scripts" checkbox.
TC server will ask you if you want to overwrite your existing settings in VCS, or instead import them:
If you select overwrite, TC will make a new commit, where all previous XML settings will be removed from tracking, and two new files will be created instead in the VCS: pom.xml and settings.kts. The latter will contain all the project/builds settings combined in one place.
If you select import TC will try to import the latest existing (XML ones) settings from the VCS. You shouldn't use this option if you want to migrate to Kotlin.
Please note that switching back from Kotlin to XML will not be possible in scope of the same project.
If you want to change your versioned settings back from Kotlin to XML, you can disable the synchronisation, save the settings, then enable in once again and select XML format. TC will make a new commit into VCS, where it will remove Kotlin files from tracking and add new XML files created from current settings instead.
We made the change to koltin. It went very smooth. Now we just have to convert our meta-runners, which looks very easy.