Skip to main content

Command Palette

Search for a command to run...

CI/CD for an ARM template using Azure DevOps

Published
1 min read
CI/CD for an ARM template using Azure DevOps
R

Hello! 👋 I'm a Cloud and DevOps enthusiast with a passion for designing, building, and managing cloud infrastructure and applications. 👩‍💻 I enjoy learning about the latest technologies and best practices in this field and believe that automation and continuous delivery are key to enabling faster and more reliable software development.

Create a new project in Azure DevOps and select the appropriate repository type

Screenshot 2023-02-18 015422

image

image

Configure the pipeline by specifying the build and deployment tasks for the application.

Screenshot 2023-02-18 015626

Save and run pipeline: Once you've completed all of the necessary configurations, save the pipeline and run it to verify that it works as expected.

Screenshot 2023-02-18 015649

Screenshot 2023-02-18 015539

Set up continuous integration (CI): To enable continuous integration, configure your pipeline to trigger automatically whenever changes are pushed to your application code repository.

Screenshot 2023-02-18 015837

Set up your build triggers by specifying when the build should be triggered

Screenshot 2023-02-18 015820

Screenshot 2023-02-18 015942

▶ GitHub Link
🔗Romeshdg/Rdg_ARM-Temp: Sample for demoing CI/CD for an ARM template using Azure DevOps (github.com)

📍 Thanks for reading, and happy learning! :) ✌

✨Let's continue to learn and grow together.

follow me on LinkedIn for more updates and insights. Also, don't forget to like, share, and comment on this post to spread the word and help others in their Learning journey.

S

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.