Hello, Igniters. Also ready to help to #MakeTeamcityGreenAgain !
21 июля 2017 г. 12:56 PM пользователь "Vyacheslav Daradur" < daradu...@gmail.com> написал: > Hi guys. > > I vote for #MakeTeamcityGreenAgain. :-) > > FYI: it had been described and supported previously[1] > > After the completion of my current task I will try to help with this > activity. > > [1] > http://apache-ignite-developers.2346864.n4.nabble. > com/Test-failures-td14353.html > > 2017-07-21 12:39 GMT+03:00 Anton Vinogradov <a...@apache.org>: > > > Nikolay, > > > > That's also a big problem for me, as reviewer, to accept changes and > merge > > them to master. > > > > Dmitriy, > > > > Currently we have some contributions *from community* blocked by red > > Teamcity. > > > > On Fri, Jul 21, 2017 at 12:47 AM, Nikolay Izhikov < > nizhikov....@gmail.com> > > wrote: > > > > > +1 to Dmitry Pavlov from me. > > > > > > Green team city would be very helpful. > > > > > > > > > > If you are a newcomer, please share your feeling: are you confused by > > > test > > > > failures on Teamcity? > > > > > > I'm working on my very first ignite issue > > > and it's not easy to understand TC build results. > > > > > > > > > 21.07.2017 00:30, Dmitriy Setrakyan пишет: > > > > > > I think the right question to ask is why do we have RED tests to begin > > >> with. In my view, TC should be green. If there are tests that do not > > pass, > > >> we should disable them and file blocker tickets for the next releases. > > >> > > >> D. > > >> > > >> On Thu, Jul 20, 2017 at 1:20 PM, Dmitry Pavlov <dpavlov....@gmail.com > > > > >> wrote: > > >> > > >> Hi Igniters, > > >>> > > >>> We all know that there are a lot of open tasks in Ignite project. To > be > > >>> able to handle all these tasks, we need to grow our community. And to > > >>> achieve that, we should pay special attention to new community > members. > > >>> > > >>> As recent newcomer I’ve faced the following problem: There is no way > to > > >>> find out by yourself whether your pull request changes are correct or > > >>> not. > > >>> Contributor can not distinguish pull request test failures and master > > >>> test > > >>> failures. Experienced Ignite contributor can estimate the damage, but > > how > > >>> it can be done by new community member? > > >>> > > >>> Once failing test is introduced to master it is multiplexed to all > > later > > >>> PRs. As a result, we have tons of failures and suites timeouts, which > > >>> waste > > >>> Teamcity agents time. > > >>> > > >>> I suggest to start new activity - MakeTeamcityGreenAgain. I’m sure > that > > >>> there are a lot of experienced developers in the community who > > understand > > >>> issues with tests very quickly. Please contact me if you are ready to > > >>> help > > >>> the community to fix current test issues. > > >>> > > >>> I would appreciate any ideas and sharing your vision how we can > achieve > > >>> green teamcity. > > >>> > > >>> If you are a newcomer, please share your feeling: are you confused by > > >>> test > > >>> failures on Teamcity? > > >>> > > >>> Sincerely, > > >>> > > >>> Dmitriy Pavlov > > >>> > > >>> > > >> > > > > > > -- > Best Regards, Vyacheslav D. >
