发表机构
Trent University; Hadhramout University; Al-Arab University（特伦特大学; 哈德拉毛大学; 阿拉伯大学）
机构由 AI 辅助整理，请以论文原文为准。AI 中文总结
本研究通过大规模纵向分析135227个GitHub仓库，揭示多CI服务采用多为迁移过渡，GitHub Actions成为主导，弃用主要受服务身份影响，为CI工具与迁移提供实证依据。
AI 中文摘要
持续集成（CI）的采用已从单一实践演变为多种竞争性服务的广阔格局，许多项目不再依赖单一的CI服务。然而，这种多服务行为在项目生命周期中如何演变仍然未知。先前的研究通过个别服务、特定语言或开发者访谈来考察CI的采用和迁移，导致多服务使用的生命周期未被充分探索。在本文中，我们对多CI服务采用进行了大规模纵向研究，覆盖了来自七种编程语言的135227个GitHub仓库，涉及八种CI服务。我们通过定量和定性分析，描述了CI服务随时间被采用、演变和弃用的特征。大约五分之一的仓库使用多种CI服务，这通常是迁移过程中的过渡状态，而非持续并行使用。CI服务的选择是影响采用、复杂性、维护和参与度的主导因素，而语言的影响仅限于特定情况。我们的结果显示，向GitHub Actions的转变是一次同步的平台级过渡，在2020年所有研究语言中首次采用的比例超过了50%，而Travis CI在其定价变更后的衰落成为最强的弃用信号。我们对CI配置理由的分析表明，活动大多是被动反应性的：只有约11%的提交陈述了战略性理由，这表明提交信息更可靠地捕获了操作维护模式，而非战略意图。最后，我们发现多CI采用主要与项目成熟度相关，而弃用则与服务身份的相关性强于仓库特征。这些发现为CI工具、迁移支持以及管理不断演变的软件交付基础设施的未来研究提供了经验证据。
英文摘要
Continuous Integration (CI) adoption has evolved from a single practice into a broad landscape of competing services, and many projects no longer rely on a single CI service. However, how this multi-service behavior evolves over a project's lifetime remains unknown. Prior work has examined CI adoption and migration through individual services, specific languages, or developer interviews, leaving the lifecycle of multi-service usage underexplored. In this paper, we conduct a large-scale longitudinal study of multi-CI service adoption covering 135227 GitHub repositories from seven programming languages and involving eight CI services. We characterize how CI services are adopted, evolved, and abandoned over time through quantitative and qualitative analyses. About one in five repositories use multiple CI services, often transitional during migration rather than for sustained parallel use. CI service choice is the dominant factor across adoption, complexity, maintenance, and engagement, with language effects limited to specific cases. Our results reveal that the shift to GitHub Actions was a synchronized platform-level transition, crossing 50\% of first adoptions in 2020 across all studied languages, while the decline of Travis CI following its pricing change became the strongest abandonment signal. Our analysis of CI configuration rationales shows that activity is mostly reactive: only about 11\% of commits state a strategic reason, indicating that commit messages capture operational maintenance patterns more reliably than strategic intent. Finally, we find that multi-CI adoption is primarily associated with project maturity, whereas abandonment is more strongly associated with service identity than repository characteristics. These findings provide empirical evidence for CI tooling, migration support, and future research on managing evolving software delivery infrastructure.
