This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
This tool monitors TeamCity https://ci.ignite.apache.org/ and send notifications to dev. list if it detects new failures.Source code available at
Ignite Developers are welcome to give feedback and post issues.
This tool can be also used for checking PR for introduction of new failures.
Analyze latest TeamCity tests results against the latest master:
Analyze latest TeamCity tests results against the other branch:
Analyze specific TeamCity build against the latest master:
Print possible blockers to the JIRA ticket:
Trigger "Run All" and comment JIRA by one button:
View and compare the statistics of "Run All" for master branch for a period of time.
Go to the Master Trends page
Select the interval and click "Apply". The minimum interval is 1 day, the maximum interval is 7 days.
The selection includes builds, the start date of which is between 00:00:01 of the first day and 23:59:59 of the last day of the interval.
By default, when the page is opened, statistics are downloaded for this week (ending today) and the previous week.
For each field of "TESTS" and "PROBLEMS" sections show general results: min - median - max. By clicking on the icon near field name will show line chart for all data this field. Cells in the "PROBLEMS" section are additionally dyed green if the current median is less than the median in the other column. If more, then red.
The TeamCity server stores information about the builds for ~ two weeks. At the end of this period, the data is deleted from the TC server. Apache Ignite Teamcity Helper saves all received data in the cache so that they are available after this time. But still some of the information may be missing. If for the whole period there is no information on any build, you will receive a message «No data for the selected period». If data are available for not all days, you will receive a message «Data for the period from DD-MM-YYYY to DD-MM-YYY» or «Data for DD-MM-YYY».
This section covers notification types utility can send to dev@ list. User can specify his or her email and select desired tracked branches. All failures in this braches will be also forwarded to user.
New test failure notification is generated if test was stable passing and then became stable failing. Stable passing test requires at least 5 sucessfull runs in a row. Stable failure requires 4 failures in a row.
Let's define 0 as success, 1 as failure.
So history of runs ..000001111.. will cause notification. First transition 0->1 can be bug introduced test failure, and notification is linked to this particular build. Notification will not be resend in case tests continues to fail. This is done because all contributors are considered as interested in successfull tests passing and will do required steps to fix issue.
Duplicate notification can occur for same test if there is history ...000001111...000001111. And second transition 0 ->1 can be potentially new problem, and test failure would be re-notified.
Some tests are flaky and sometimes change its state. This means test can be unluckily failed 4 times in a row. To protect from spam the Bot checks if fail row is happened on the one commit. If yes - test fail is considered as fail for 8 failures in a row. So history should be at least ...0000011111111...
If test has no previous history and failed 4 times in a row, then it is considered as newly introduced failure.
The Bot is able to handle timeouts & JVM crashes in suites in a special way. These type of failures are named Critical. If 4 or more (timeouts/JMV crashes) occured several times in a row, this will generate suite-related notification. Also it is required that last run was completed with timeout.
Lets name result 2 as critical failure. So it is required to have 5 non critical failures and 4 critical to generate notification: ....(0/1)(0/1)(0/1)(0/1)(0/1) 2222....
Please see Github integrated documentation on how to contribute: https://github.com/apache/ignite-teamcity-bot#development