That is a great idea if you understand what you are doing. And awful if not.
Currently - settings for all Apache Ignite build projects on TeamCity are ALREADY stored as code in GitHub, as a PMC member you have access to https://github.com/apache-ignite-teamcity/configuration. Though the initial configuration is still done via UI, you can already start modifying code in the aforementioned repository, yet in XML, and changes will be automatically loaded and appear in UI. Also, I should disappoint you in your idea to test settings in branches - TC does not entirely support this feature, at least new build configurations or changes in snapshot dependencies are not visible and sometimes are not loaded from branch. What we can do now - we can start transferring projects one by one very carefully, and, as a first step, consider only the idea of changing settings via code (using Kotlin for instance) while implementing "one project - one repo" approach (due to another limitation of TeamCity's VCS stored settings). Also, old/obsolete projects should not be touched and continue to use current UI-based settings configuration until final end of life or entire deprecation. чт, 19 дек. 2024 г. в 15:21, Mirza Aliev <alievmi...@gmail.com>: > Great idea! > > I remember that something similar was planned by Peter Ivanov; it would be > nice to hear his thoughts on that. > > чт, 19 дек. 2024 г. в 14:33, Maksim Myskov <mys...@apache.org>: > > > This is definitely needs to be done. > > -- > > Maksim Myskov > > > > > On 19 Dec 2024, at 12:56, Pavel Tupitsyn <ptupit...@apache.org> wrote: > > > > > > Igniters, > > > > > > Currently, our TeamCity projects [1] are UI-defined and are the same > for > > > all branches. > > > Which has the following issues: > > > - Can't test project changes in a branch without risking broken main > > > - Can't have different settings for different branches (e.g. SDK > upgrade > > in > > > a new version only) > > > - Difficult to manage and review the changes in TeamCity UI > > > > > > The solution is to store the project settings in Git along with the > rest > > of > > > the code [2]. > > > I suggest adopting this approach for ignite-3 repo. > > > > > > Thoughts, objections? > > > > > > > > > [1] > > > > > > https://ci.ignite.apache.org/project/ApacheIgnite3xGradle?branch=%3Cdefault%3E&buildTypeTab=overview&mode=builds#all-projects > > > > > > [2] > > > > > > https://www.jetbrains.com/help/teamcity/storing-project-settings-in-version-control.html > > > > >
