Project: SonarSource/sonar-java


This report was generated at 2018-08-16 19:47:18 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 -

Downtrend: during the last 90 days, your build duration decreased by 1.45%






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.


↗ Uptrend -

During the last 90 days, the number of broken release builds increased by 46.27%




During the last 90 days your master was broken 35 times. On average, it took you 1.63 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: Fail_check_test_if_exception
Severity Description
High In your project, branches are typically synced with master every 19.54 hours. However, branch Fail_check_test_if_exception has last synced with master on 2018-02-14 15:31:26, and branch UCFG_generator has commits that are 12.95 weeks newer than that.
High Your latest commits were performed on branch SONARJAVA-2850 on 2018-08-13 15:26:56. However, your last changes on branch Fail_check_test_if_exception happened 25.71 weeks ago, and have not been merged yet. In your project, you typically merge branches within 5.99 weeks.
High In your project, branches do not deviate for more than 5.99 weeks. However, you are working on branch Fail_check_test_if_exception since 15549537s (~25.71 weeks) without synchronization.

Issues found for branch: Fix-Coverage-S3366
Severity Description
High In your project, branches are typically synced with master every 19.54 hours. However, branch Fix-Coverage-S3366 has last synced with master on 2018-03-15 10:46:47, and branch UCFG_generator has commits that are 8.84 weeks newer than that.
High Your latest commits were performed on branch SONARJAVA-2850 on 2018-08-13 15:26:56. However, your last changes on branch Fix-Coverage-S3366 happened 21.6 weeks ago, and have not been merged yet. In your project, you typically merge branches within 5.99 weeks.
High In your project, branches do not deviate for more than 5.99 weeks. However, you are working on branch Fix-Coverage-S3366 since 13061016s (~21.6 weeks) without synchronization.

Issues found for branch: Fix_S1312
Severity Description
High In your project, branches are typically synced with master every 19.54 hours. However, branch Fix_S1312 has last synced with master on 2018-03-16 09:39:17, and branch UCFG_generator has commits that are 8.7 weeks newer than that.
High Your latest commits were performed on branch SONARJAVA-2850 on 2018-08-13 15:26:56. However, your last changes on branch Fix_S1312 happened 21.46 weeks ago, and have not been merged yet. In your project, you typically merge branches within 5.99 weeks.
High In your project, branches do not deviate for more than 5.99 weeks. However, you are working on branch Fix_S1312 since 12978666s (~21.46 weeks) without synchronization.

Issues found for branch: MishaDemianenko_fixS2293
Severity Description
High In your project, branches are typically synced with master every 19.54 hours. However, branch MishaDemianenko_fixS2293 has last synced with master on 2018-01-10 10:18:01, and branch UCFG_generator has commits that are 17.99 weeks newer than that.
High Your latest commits were performed on branch SONARJAVA-2850 on 2018-08-13 15:26:56. However, your last changes on branch MishaDemianenko_fixS2293 happened 30.74 weeks ago, and have not been merged yet. In your project, you typically merge branches within 5.99 weeks.
High In your project, branches do not deviate for more than 5.99 weeks. However, you are working on branch MishaDemianenko_fixS2293 since 18592342s (~30.74 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