Hi, Dmitry.
I think we should start with adding current projects as-is in form of autogenerated Kotlin code, but continue to use UI for editing. Later at some point we should replace autogenerated code with valid one (this can be done configuration by configuration), that will allow use the power of DSL and programming language to create dynamic configuration and use other benefits. Also, while I was thinking about it, I wondered — should we add whole TC config to single repository, or divide per project (AI 2.x, AI 3.x, Extensions, Thin Clients, etc.) and add corresponding TeamCity configuration as part of the project into the same repository. TeamCity configuration is added in form of maven project in .teamcity directory in the project's root and will not interfere with the project itself. Also this scheme is preferable due to linear development cycle (no parallel versions in development for each project). I think I am ready to drive this initiative when and if we agree on this matter and will discuss all the details of such migration. > On 16 Aug 2021, at 19:36, Dmitry Pavlov <dpav...@apache.org> wrote: > > Hi Igniters, > > Once there was a discussion about placing our build configurations (TC) > settings in a VSC repository. This idea was suggested because we wanted to > validate internals of configs using IDE/text editor. > > https://www.jetbrains.com/help/teamcity/storing-project-settings-in-version-control.html > > Now, with introduction of a second instance this idea migth be useful twice, > we'll be able to > - view, track history, track authorship (? I'm not 100% sure, it is to be > checked) > - use VSC as a signle source of thurth > - we can remove TC Bot's code for validating all configs using REST > > How does that sound to you? Is it better to look at Kotlin DSL? Or could XML > be enought? > > Sincerely, > Dmitriy Pavlov >
