Continuous Integration and Continuous Delivery in the Process of Developing Robotic Systems

Rashitov, Vadim; Ivanou, Mikhail

doi:10.1007/978-3-030-29852-4_29

Cited by 6 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…CI/CD services automatically compile and link a code repository and then build the software into a deliverable package. Their use in the robotics domain is gradually becoming more popular, yet they are still underutilized when compared to other fields of software development [8], [13].…”

Section: Building From the Sourcementioning

confidence: 99%

“…To overcome these issues, we present a simple workflow based on continuous integration and continuous delivery (CI/CD) techniques [8] for producing an executable version of a code repository that can be downloaded and run in a straightforward way. Moreover, the executable package is automatically generated from the last version of the source code and archived together with the code repository.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Run to the Source: The Effective Reproducibility of Robotics Code Repositories

Cervera

2024

IEEE Robot. Automat. Mag.

View full text Add to dashboard Cite

In recent years the robotics community has actively embraced the open paradigm, and research articles are commonly enriched with the inclusion of a source code repository of software. However, the reproducibility of such code is not straightforward, and it may become increasingly difficult with the evolution of software. There is a need for providing not only the source code but also an executable version with all of the necessary library dependencies. A solution based on software containers is presented in this article, with some unique advantages. First, the executable package is automatically generated from the last version of the source code; second, it is archived in the same cloud service that hosts the code repository; third, it integrates seamlessly with the development workflow of the research code; finally, it does not consume any local computing resources from the researcher. The executable code can then be downloaded and run by other users, with the only requirement being installing a specific software for running containers. This article presents the complete workflow, which is then applied to some illustrative examples of source code repositories of articles published at robotics conferences.

show abstract

Section: Building From the Sourcementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%