You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2017/10/23 12:07:00 UTC

[jira] [Resolved] (OAK-6855) Researching Build Breakage

     [ https://issues.apache.org/jira/browse/OAK-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-6855.
-----------------------------------
    Resolution: Not A Problem

> Researching Build Breakage
> --------------------------
>
>                 Key: OAK-6855
>                 URL: https://issues.apache.org/jira/browse/OAK-6855
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Dereck
>            Priority: Minor
>
> Dear developers of the jackrabbit-oak project,
> We are MSc students from the Delft University of Technology doing research on why builds break in open source projects. To do this, we are analyzing Travis build statistics and build history of jackrabbit-oak.
> By analyzing the build history of jackrabbit-oak, we found the following:
> * The project has 45% failing builds in the history
> * The project has a high amount of build failures compared to other similar projects
> When looking at jackrabbit-oak’s build metrics, we could not find clear factors that are highly correlated with this result.
> To identify the reasons behind build breakage, we would like to collect developer insights into the reasons why build breakage occurs. If you have five minutes, please answer the [survey|https://www.surveymonkey.com/r/PQ7XTGM] we have created. Your response will be very useful in our study.
> Thank you.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)