Hi Maxim,
Sure, thank you for this idea.
I've accumulated notification types and rules here:
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-NotificationTypes
Sincerely,
Dmitriy Pavlov
ср, 18 июл. 2018 г. в 13:59, Maxim Muzafarov :
>
Dmitry,
Got it. Thanks!
I've found brief MTCGABot description here [1].
Can we also add there this notification rules?
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
ср, 18 июл. 2018 г. в 12:52, Dmitry Pavlov :
> Hi Maxim,
>
>
Hi Maxim,
Notification will be send for each sequential group of builds having
failures 3+ times in a row. Let's define 0 as success, 1 as failure.
So history 01110111 will generate two notifications. First
transition 0->1 can be bug introduced test failure. This bug can be fixed
with
Odd flaky tests notifications were fixed.
If test changes its status more than 6 times in last 50 runs, than it is
required to fail 7 times in a row to be considered as new failure. Normal
test can be considered as new failure if it fails 3 times.
I would appreciate any feedback and proposals of
Hi Igniters,
Seems this test is flaky: it has frequent changes of its status. This can
be detected in Bot. and I'll update Bot once issue
https://github.com/dspavlov/ignite-teamcity-helper/issues/14 is completed.
So please ignore this failure for now, as it is not new. Of course if you
know how
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
CacheStopAndDestroySelfTest.testTckStyleCreateDestroyClose
