Project: scijava/scijava-common


This report was generated at 2018-08-16 19:51:03 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.


↗ Uptrend -

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




Possible problems found in recent builds on your branches:

Severity Branch Date Build Duration Description
Medium master 2018-08-02 13:11:55 411277743 2.7 minutes This build is slower than 84.62% of your builds on master


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.




During the last 90 days your master was broken 3 times. On average, it took you 6.3 days 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’


No late merging warnings found!


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