基于示例的持续集成系统自动迁移
Example-Based Automatic Migration of Continuous Integration Systems
AI总结:
提出基于示例挖掘的 CIMig,从迁移实例学习规则与配置模式,实现 Travis CI 与 GitHub Actions 的双向自动迁移,并在 251 个项目上验证其有效性。
摘要:
持续集成(Continuous Integration,CI)是一种被广泛采用的实践,用于更快地进行代码变更集成和测试。开发者经常会在不同 CI 系统之间迁移,以追求矩阵构建或更好的日志记录等功能。然而,由于对新 CI 系统及其语法了解有限,这种迁移耗费大量精力且容易出错。此外,这些迁移需要多次迭代和大量时间才能在新 CI 系统中实现稳定,而目前对 CI 配置自动迁移的支持仍不充分。为缓解这些问题,我们提出了一种用于 CI 系统自动迁移的新方法:CIMig。我们的方法利用基于示例的挖掘,从现有迁移示例中提取翻译规则和配置模式,并利用它们在新的上下文中复现这种迁移。为了从实证角度验证和评估我们的方法,我们将其应用于 Travis CI 与 GitHub Actions 之间的迁移。我们从 1001 个项目中收集学习经验,随后将其应用于迁移包含 251 个项目的评估集。这帮助我们对 CIMig 进行了定性和定量评估,并通过将结果与基于手动规则的 GitHub Actions Importer 的结果进行比较来说明结果背景。此外,我们的工具生成的文件获得了开发者的良好评价,并且与这些相同项目的手动迁移相比,平均为开发者节省了 42.4 分钟。我们的基于学习的方法也更加灵活,这一点已通过我们能够将其应用于把 GitHub Actions 文件迁移到 Travis 而得到证明,而 GitHub Actions Importer 无法做到这一点。我们认为 CIMig 是同类方法中首个用于迁移 CI 系统的方法,并且可以应用于其他软件配置系统迁移。我们的复现包可在 [5] 获取。
英文摘要:
Continuous Integration (CI) is a widely adopted practice for faster code change integration and testing. Developers often migrate between CI systems in pursuit of features like matrix building or better logging. However, this migration is effort intensive and error-prone owing to limited knowledge of the new CI system and its syntax. Moreover, these migrations require multiple iterations and significant time to achieve stability in the new CI system, and there is insufficient support for the automatic migration of CI configurations. To mitigate this, we propose a novel approach for CI system's automatic migration: CIMig. Our approach utilizes Example-Based mining, where it extracts translation rules and configuration patterns from existing migration examples, and employs them to reproduce this migration in new contexts. To empirically validate and evaluate our approach, we apply it to the migration between Travis CI and GitHub Actions. We gathered learnings from 1001 projects, and then applied them to migrate an evaluation set of 251 projects. This helped us perform a qualitative and quantitative evaluation of CIMig, and we contextualize our results by comparing them with those of the manual-rule-based GitHub Actions Importer. Furthermore, our tool generated files that were rated favorably by developers and saved them an average of 42.4 minutes over the manual migration of these same projects. Our learning-based approach is also more flexible, as proven by our ability to apply it to migrate GitHub Actions files to Travis, which GitHub Actions Importer can not do. We believe CIMig is the first approach of its kin to migrate CI systems and can be applied to other software configuration system migrations. Our replication package is available at [5].
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。