Sounds great, are you going to drive this activity? On Thu, Dec 19, 2024 at 11:57 AM 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 > -- With regards, Aleksandr Polovtsev
