Project: Graylog2/graylog2-server


This report was generated at 2018-08-18 13:48:04 UTC. We have analyzed the CI history of your project from your Travis-CI build logs and your GitHub repository and have checked several dimensions of your CI process to find deviations from accepted best practices. In the following, you will find the results of our analysis.

We would highly appreciate your feedback and constructive comments on this report. This helps us to evaluate the idea and to further improve the report in the future. Please consider taking the following quick survey


Slow builds

Build times can increase due to high workload of the build server or due to increased project complexity over time. In fact, slow-down is often hard to detect, because it slowly creeps into the project. A slow build causes wait times for developers, adds a large overhead to the whole process, and should be avoided. Our summary provides an overview over recent build times and reports recent cases, in which the build duration takes substantially longer than usual.


→ Stable -

During the last 90 days, your build duration increased by 5.15%




Possible problems found in recent builds on your branches:

Severity Branch Date Build Duration Description
Medium master 2018-08-17 14:20:54 417286391 27.35 minutes This build is slower than 77.10% of your builds on master
Medium StoreProviderMock 2018-07-27 09:32:25 408866209 28.52 minutes This build is slower than 86.45% of your builds on master
Medium content-pack-install 2018-07-27 08:53:31 408853154 27.27 minutes This build is slower than 75.23% of your builds on master
Medium csrf-prevention 2018-08-09 15:07:01 414106069 28.15 minutes This build is slower than 85.05% of your builds on master
Medium csrf-protection-25 2018-08-15 15:34:07 416412397 45.98 minutes This build is slower than 99.53% of your builds on master
Medium fix-content-pack-entity-table-titles 2018-08-01 14:24:06 410834659 28.92 minutes This build is slower than 88.79% of your builds on master
Medium issue-4861-4859 2018-06-28 07:24:40 397673056 35.73 minutes This build is slower than 98.13% of your builds on master
Medium issue-4876 2018-06-28 08:45:18 397694876 27.35 minutes This build is slower than 77.10% of your builds on master
Medium issue-4935 2018-08-13 15:06:51 415491280 29.9 minutes This build is slower than 94.39% of your builds on master
Medium issue-4935-2 2018-08-17 12:04:44 417233686 29.23 minutes This build is slower than 90.65% of your builds on master
Medium issue-4941 2018-08-17 12:25:22 417240892 28.82 minutes This build is slower than 88.32% of your builds on master
Show more…



Broken release branch

The CI pipeline requires a working build to properly assess whether changes introduce a problem, so recovering the build is the highest team priority. A build on the release branch typically also involves the deployment of the build results and should never fail. Our summary provides an overview over the number of recent release-branch failures and indicates the trend over time.


→ Stable -

During the last 90 days, the number of broken release builds increased.




During the last 90 days your master was broken 39 times. On average, it took you 6.95 hours to fix it again.



Skip failed tests

Having an elaborated test-suite is one of the pillars of continuous integration. It provides protection from invalid changes and failing tests have to be taken seriously. Deleting or skipping a failing test might fix a broken build, but it is a removal of the symptom rather than a fix of the root cause and should be avoided.


No skip test warnings found!



Late merging

Benefits of CI diminish, when individual feature branches are synchronized sparsely or when they are too long-lived. We point out several scenarios in our reports that might indicate such a ‘Late Merging’


Issues found for branch: 3318
Severity Description
High In your project, branches are typically synced with master every 2.03 days. However, branch 3318 has last synced with master on 2018-01-31 15:27:38, and branch disable-flakey-test has commits that are 15.81 weeks newer than that.
High Your latest commits were performed on branch provide-user-and-roles-helpers-for-migrations on 2018-08-17 12:51:19. However, your last changes on branch 3318 happened 28.27 weeks ago, and have not been merged yet. In your project, you typically merge branches within 9.15 weeks.
High In your project, branches do not deviate for more than 9.85 weeks. However, you are working on branch 3318 since 17106609s (~28.28 weeks) without synchronization.

Issues found for branch: ForkedBooter-macos
Severity Description
High In your project, branches are typically synced with master every 2.03 days. However, branch ForkedBooter-macos has last synced with master on 2018-03-16 11:59:25, and branch disable-flakey-test has commits that are 9.54 weeks newer than that.
Medium Your latest commits were performed on branch provide-user-and-roles-helpers-for-migrations on 2018-08-17 12:51:19. However, your last changes on branch ForkedBooter-macos happened 22.01 weeks ago, and have not been merged yet. In your project, you typically merge branches within 9.15 weeks.
Medium In your project, branches do not deviate for more than 9.85 weeks. However, you are working on branch ForkedBooter-macos since 13317502s (~22.02 weeks) without synchronization.

Issues found for branch: GrokHelper
Severity Description
High You have been working on GrokHelper for 4.55 weeks.Your feature branches are typically open for 2.03 days.

Issues found for branch: StoreProviderMock
Severity Description
High You have been working on StoreProviderMock for 1.55 weeks.Your feature branches are typically open for 2.03 days.

Issues found for branch: add-bootstrap-modal-confirm
Severity Description
High In your project, branches are typically synced with master every 2.03 days. However, branch add-bootstrap-modal-confirm has last synced with master on 2018-03-23 16:20:51, and branch disable-flakey-test has commits that are 8.52 weeks newer than that.
Medium Your latest commits were performed on branch provide-user-and-roles-helpers-for-migrations on 2018-08-17 12:51:19. However, your last changes on branch add-bootstrap-modal-confirm happened 20.98 weeks ago, and have not been merged yet. In your project, you typically merge branches within 9.15 weeks.
Medium In your project, branches do not deviate for more than 9.85 weeks. However, you are working on branch add-bootstrap-modal-confirm since 12697016s (~20.99 weeks) without synchronization.

Show more…

Tip: Frequently synchronized branches are easier to integrate.
Tip: Break features into smaller tasks to finish them faster.

Thanks for reading the summary! Please now fill our quick survey