The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study

Continuous Integration (CI) is a software development practice that leads developers to integrate their work more frequently. Software projects have broadly adopted CI to ship new releases more frequently and to improve code integration. The adoption of CI is usually motivated by the allure of de...

ver descrição completa

Na minha lista:
Detalhes bibliográficos
Autor principal: Bernardo, João Helis Júnior de Azevedo
Outros Autores: Kulesza, Uira
Formato: Dissertação
Idioma:por
Publicado em: Brasil
Assuntos:
Endereço do item:https://repositorio.ufrn.br/jspui/handle/123456789/24208
Tags: Adicionar Tag
Sem tags, seja o primeiro a adicionar uma tag!
id ri-123456789-24208
record_format dspace
institution Repositório Institucional
collection RI - UFRN
language por
topic Integração contínua
Desenvolvimento baseado em Pull Requests
Pull Request
Tempo de entrega
Atraso de entrega
Mineração de repositórios de software
CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO::SISTEMAS DE COMPUTACAO
spellingShingle Integração contínua
Desenvolvimento baseado em Pull Requests
Pull Request
Tempo de entrega
Atraso de entrega
Mineração de repositórios de software
CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO::SISTEMAS DE COMPUTACAO
Bernardo, João Helis Júnior de Azevedo
The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
description Continuous Integration (CI) is a software development practice that leads developers to integrate their work more frequently. Software projects have broadly adopted CI to ship new releases more frequently and to improve code integration. The adoption of CI is usually motivated by the allure of delivering new software content more quickly and frequently. However, there is little empirical evidence to support such claims. Over the last years, many available software projects from social coding environments such as GitHub have adopted the CI practice using CI facilities that are integrated in these environments (e.g., Travis-CI). In this dissertation, we empirically investigate the impact of adopting CI on the time-to-delivery of pull requests (PRs), through the analysis of 167,037 PRs of 90 GitHub projects that are implemented in 5 different programming languages. On analyzing the percentage of merged PRs per project that missed at least one release prior being delivered to the end users, the results show that before adopting CI, a median of 13.8% of merged PRs are postponed by at least one release, while after adopting CI, a median of 24% of merged PRs have their delivery postponed to future releases. Contrary to what one might speculate, we find that PRs tend to wait longer to be delivered after the adoption of CI in the majority (53%) of the studied projects. The large increase of PR submissions after CI is a key reason as to why these projects deliver PRs more slowly after adopting CI. 77.8% of the projects increase the rate of PR submissions after adopting CI. To investigate the factors that are related to the time-to-delivery of merged PRs, we train linear and logistic regression models, which obtain sound median R-squares of 0.72-0.74, and good median AUC values of 0.85-0.90. A deeper analysis of our models suggests that, before and after the adoption of CI, the intensity of code contributions to a release may increase the delivery time due to a higher integration-load (in terms of integrated commits) of the development team. Finally, we are able to accurately identify merged pull requests that have a prolonged delivery time. Our regression models obtained median AUC values of 0.92 to 0.97.
author2 Kulesza, Uira
author_facet Kulesza, Uira
Bernardo, João Helis Júnior de Azevedo
format masterThesis
author Bernardo, João Helis Júnior de Azevedo
author_sort Bernardo, João Helis Júnior de Azevedo
title The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
title_short The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
title_full The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
title_fullStr The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
title_full_unstemmed The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
title_sort impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study
publisher Brasil
publishDate 2017
url https://repositorio.ufrn.br/jspui/handle/123456789/24208
work_keys_str_mv AT bernardojoaohelisjuniordeazevedo theimpactofadoptingcontinuousintegrationonthedeliverytimeofmergedpullrequestsanempiricalstudy
AT bernardojoaohelisjuniordeazevedo impactofadoptingcontinuousintegrationonthedeliverytimeofmergedpullrequestsanempiricalstudy
_version_ 1773965084619440128
spelling ri-123456789-242082022-04-12T22:11:55Z The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study Bernardo, João Helis Júnior de Azevedo Kulesza, Uira http://lattes.cnpq.br/7977641264944574 http://lattes.cnpq.br/0189095897739979 http://lattes.cnpq.br/0189095897739979 Costa, Daniel Alencar da http://lattes.cnpq.br/4134189443162798 Aranha, Eduardo Henrique da Silva http://lattes.cnpq.br/9520477461031645 Maia, Marcelo de Almeida http://lattes.cnpq.br/4915659948263445 Coelho, Roberta de Souza http://lattes.cnpq.br/9854634275938452 Integração contínua Desenvolvimento baseado em Pull Requests Pull Request Tempo de entrega Atraso de entrega Mineração de repositórios de software CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO::SISTEMAS DE COMPUTACAO Continuous Integration (CI) is a software development practice that leads developers to integrate their work more frequently. Software projects have broadly adopted CI to ship new releases more frequently and to improve code integration. The adoption of CI is usually motivated by the allure of delivering new software content more quickly and frequently. However, there is little empirical evidence to support such claims. Over the last years, many available software projects from social coding environments such as GitHub have adopted the CI practice using CI facilities that are integrated in these environments (e.g., Travis-CI). In this dissertation, we empirically investigate the impact of adopting CI on the time-to-delivery of pull requests (PRs), through the analysis of 167,037 PRs of 90 GitHub projects that are implemented in 5 different programming languages. On analyzing the percentage of merged PRs per project that missed at least one release prior being delivered to the end users, the results show that before adopting CI, a median of 13.8% of merged PRs are postponed by at least one release, while after adopting CI, a median of 24% of merged PRs have their delivery postponed to future releases. Contrary to what one might speculate, we find that PRs tend to wait longer to be delivered after the adoption of CI in the majority (53%) of the studied projects. The large increase of PR submissions after CI is a key reason as to why these projects deliver PRs more slowly after adopting CI. 77.8% of the projects increase the rate of PR submissions after adopting CI. To investigate the factors that are related to the time-to-delivery of merged PRs, we train linear and logistic regression models, which obtain sound median R-squares of 0.72-0.74, and good median AUC values of 0.85-0.90. A deeper analysis of our models suggests that, before and after the adoption of CI, the intensity of code contributions to a release may increase the delivery time due to a higher integration-load (in terms of integrated commits) of the development team. Finally, we are able to accurately identify merged pull requests that have a prolonged delivery time. Our regression models obtained median AUC values of 0.92 to 0.97. Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq) A Integração Contínua (IC) é uma prática de desenvolvimento de software que leva os desenvolvedores a integrarem seu código-fonte mais frequentemente. Projetos de software têm adotado amplamente a IC com o intuito de melhorar a integração de código e lançar novas releases mais rapidamente para os seus usuários. A adoção da IC é usualmente motivada pela atração de entregar novas funcionalidades do software de forma mais rápida e frequente. Todavia, há poucas evidências empíricas para justificar tais alegações. Ao longo dos últimos anos, muitos projetos de software disponíveis em ambientes de codificação social, como o GitHub, tem adotado a prática da IC usando serviços que podem ser facilmente integrados nesses ambientes (por exemplo, Travis-CI). Esta dissertação investiga empiricamente o impacto da adoção da IC no tempo de entrega de pull requests (PRs), através da análise de 167.037 PRs de 90 projetos do GitHub que são implementados em 5 linguagens de programação diferentes. Ao analisar a porcentagem de merged PRs por projeto que perderam pelo menos uma release antes de serem entregues aos usuários finais, os resultados mostraram que antes da adoção da IC, em mediana 13.8% dos merged PRs tem sua entrega adiada por pelo menos um release, enquanto que após a adoção da IC, em mediana 24% dos merged PRs tem sua entrega adiada para futuras releases. Ao contrário do que se pode especular, observou-se que PRs tendem a esperar mais tempo para serem entregues após a adoção da IC na maioria (53%) dos projetos investigados. O grande aumento das submissões de PRs após a IC é uma razão fundamental para que projetos demorem mais tempo para entregar PRs depois da adoção da IC. 77,8% dos projetos aumentam a taxa de submissões de PRs após a adoção da IC. Com o propósito de investigar os fatores relacionados ao tempo de entrega de merged PRs, treinou-se modelos de regressão linear e logística, os quais obtiveram R-Quadrado mediano de 0.72-0.74 e bons valores medianos de AUC de 0.85-0.90. Análises mais profundas de nossos modelos sugerem que, antes e depois da adoção da IC, a intensidade das contribuições de código para uma release pode aumentar o tempo de entrega de PRs devido a uma maior carga de integração (em termos de commits integrados) da equipe de desenvolvimento. Finalmente, apresentamos heurísticas capazes de identificar com precisão os PRs que possuem um tempo de entrega prolongado. Nossos modelos de regressão obtiveram valores de AUC mediano de 0.92 a 0.97. 2017-11-07T22:16:31Z 2017-11-07T22:16:31Z 2017-07-31 masterThesis BERNARDO, João Helis Júnior de Azevedo. The impact of adopting continuous integration on the delivery time of merged pull requests: an empirical study. 2017. 96f. Dissertação (Mestrado em Sistemas e Computação) - Centro de Ciências Exatas e da Terra, Universidade Federal do Rio Grande do Norte, Natal, 2017. https://repositorio.ufrn.br/jspui/handle/123456789/24208 por Acesso Aberto application/pdf Brasil UFRN PROGRAMA DE PÓS-GRADUAÇÃO EM SISTEMAS E COMPUTAÇÃO