Hi, I would like to understand following. We are going to make TC green. We are going to make TC fast. Are we going to do it in parallel? пн, 19 нояб. 2018 г. в 08:39, Petr Ivanov <[email protected]>: > > Concerning current TeamCity compute capacity — I think we should invest into > it’s stability at first: there are lots of problems associated with > — tests hangs (which now can render agent useless up to 3 days) > — checkout issues (speedup proxy is installed but sometimes even it is not > enough for checkout on 100 agents simultaneously, server side checkout > research is required) > — tests architecture (current one relies heavily on large file movement over > network which also can be a bottleneck in case of 100 agents simultaneous > download start) > And so on. > > After it additional donation can be discussed. > > > On 16 Nov 2018, at 17:05, Vyacheslav Daradur <[email protected]> wrote: > > > > At one of the meetups, Vladimir Ozerov has said that we may specify > > and move less risky to be broken tests in separate build plan which > > will be executed daily or weekly > > > > For example tests of compatibility with different JDK versions or > > compatibility between Ignite's releases. > > > > Also, I agree with Denis we should find and remove tests with the same > > checks. > > > > By the way, if someone of the community donates TC agents, can this > > help to reduce the time? > > > > On Thu, Nov 15, 2018 at 5:38 PM Yakov Zhdanov <[email protected]> wrote: > >> > >> Denis, you can go even further. E.g. you can start topology once for the > >> full set of single threaded full api cache tests. Each test should start > >> cache dynamically and run it logic. > >> > >> As for me, I would think of splitting RunAll to 2 steps - one containing > >> basic tests and another with more complex tests. 2nd step should not start > >> (except manually) if 1st step results in any build failure. > >> > >> --Yakov > > > > > > > > -- > > Best Regards, Vyacheslav D. >
-- Best regards, Ivan Pavlukhin
