Hi, Nikolay.
Currently, I know only how to sync build settings — we should move to Kotlin. But that is not an easy task — lots of code should be written before we can move, several repositories established and so on. Considering server instance settings like user database — tempted DB admin is required to prepare custom scripts that will replicate users info directly in database (and script maintenance will also be required due to annual DB scheme migration). > On 21 Oct 2021, at 16:51, Nikolay Izhikov <nizhi...@apache.org> wrote: > > Hello, Igniters. > > As you may know, recently, Sberbank sponsored servers capacity to setup new > instance of Team City [1] to run Ignite tests. > > Right now, ci2 is fully ready for daily usage. > We have exported and prepared Kotlin scripts [2] to keep TC settings as a > code [3]. > > I think we should adjust both TC instances to use the same settings and run > tests in the same way. > > ci.ignite.apache.org is sponsored and run by Grid Gain so > > Denis, Valentin, Petr, let's have a call to discuss how and when we can > implement these changes? > > [1] https://ci2.ignite.apache.org > [2] https://github.com/willy983/ci_tc_configuration > [3] https://www.jetbrains.com/help/teamcity/kotlin-dsl.html > > >> 3 авг. 2021 г., в 18:33, Dmitry Pavlov <dpav...@apache.org> написал(а): >> >> Hi Igniters, >> >> I'm glad to announce that SberTech made an internal aggreement to sponsor a >> computing power to provide backup TeamCity instance. This instance is >> intended to be a geo-independent, secondary instance with availablility for >> community members. >> >> Thanks to JetBrains for providing license keys for TeamCity as their part of >> opensource sponsoring program. >> >> Most likely, we'll setup some domain name as tc.i.a.o or ci2.i.a.o. Please >> share your vision what would be most obvious. >> >> After a private discussions with Vitaliy Osipov and Petr Ivanov, I do >> believe that it would be possible to preserve current registered users. >> Build configurations are to be the same for the secondary instance. >> Technical details on how is could be achieved will be available later (most >> likely we'll start a sepearate thread to dicuss that). >> >> You are more than welcome to be an early adopters. >> >> Sincerely, >> Dmitriy Pavlov >> >
