Investigation for a CI/CD Pipeline

[Sourland]

Investigation for a CI/CD Pipeline

Objective

Conduct a thorough investigation to determine the optimal CI/CD pipeline setup that accommodates the unique requirements of an STM32 embedded project running FreeRTOS and custom driver firmware.

Tasks

• Research best practices for CI/CD in embedded systems development.
• Evaluate CI/CD tools and platforms for compatibility with STM32 and FreeRTOS.
• Explore potential for cross-compilation and simulation tools integration.
• Investigate static code analysis and automated testing tools suitable for embedded C.
• Assess feasibility and resources needed for setting up hardware in the loop testing.
• Document findings with pros and cons for different CI/CD pipeline configurations.

Acceptance Criteria

• Comprehensive report on CI/CD pipeline options for STM32 embedded projects.
• Clear recommendations with justifications based on research findings.
• Identified set of tools and processes to automate building, testing, and deployment.

[giatats]

CI/CD on Raspberry pi 4B using Jenkins

• Cppcheck for static code analysis.
• Webhookrelay to trigger Jenkins remotely via Github operations.

To Do

• Discuss which parts of the code should be on the static analysis.
• Add HIL tests.
• Test Github triggers.
• Migrate Jenkins pipeline file from Jenkins enviroment directly inside the repo.

[AndronikosKostas]

@giatats what's our plan for this eventually?

[giatats]

It's done, we use Jenkins. I can demonstrate in the PeakSat's server-pc

[maestroque]

@giatats is there a link of the github actions yaml in some repo? We could also consider adding a check-build with the cross compiler. It had been done on AcubeSAT