CI/CD for an ARM template using Azure DevOps
Create a new project in Azure DevOps and select the appropriate repository type
Configure the pipeline by specifying the build and deployment tasks for the application.
Save and run pipeline: Once you've completed all of the necessary configurati...
romesh-blog.hashnode.dev1 min read
I am looking for the most suitable CI pipeline for my team. We have private and public repos on Github. We use tools such as VSCode, CubeIDE, µVision IDE for our development environment. We use various Cortex M-based MCUs for IoT applications.
Arm leads us to Arm Virtual Hardware. It is worrying that AVH is still in beta version and the sequential steps have not been updated. For example, I realised that there is not enough up-to-date documentation and hardware support for Cortex M7 based MCUs. Which CI tool do you think would be less worrying to use for public and private team repositories? Especially for the build phase? Which/which of Azure, AWS Cloud, Github Actions, Docker, CircleCI, ARM AVH etc. provide more optimised support for embedded systems. I am especially curious about the advantages and disadvantages. Is there a guide you can recommend for these issues?
Please let me know if I am not clear enough, I can give more details. Thank you for your comments in advance.