Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create real-time buildfarm structure #38

Open
carlossvg opened this issue Apr 8, 2022 · 0 comments
Open

Create real-time buildfarm structure #38

carlossvg opened this issue Apr 8, 2022 · 0 comments
Assignees

Comments

@carlossvg
Copy link
Contributor

carlossvg commented Apr 8, 2022

The current proposal is to separate the buildfarm infrastructure in different repositories so create a flexible design.

  • ros_realtime_benchmarks_config: Contains configuration files and scripts to run and generate the reports for all the different supported ROS 2 real-time benchmark tools: pendulum_control, perf_test, reference_system
  • ros_reatime_buildfarm_config: This repository contains all of the scripts and resources for running batch CI jobs of the real-time build farm. We could add here jobs for github, github local runners, gitlab, jenkins, etc. This repo is inspired by ros_buildfarm_config.
  • ros_realtime_buildfarm: Deploys an example implementation of the ros_reatime_buildfarm_config for the real-time working group use case. Ultimatetly, this will trigger benchmarks in a RPI4 monthly. This repo is inspired by ros_buildfarm.
  • ros_realtime_benchmark_reports: This repo contains the experiment results and reports for the real-time working group. Also, it will generate a website to visualize the reports in html format using github pages.
  • ros_realtime_benchmarks_test: This repo contains some tests to analyze the results from the benchmarks. For example a pytest to analyze the results and return pass or fail.

Untitled Diagram drawio

Connected to: #35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants