IAR Build Tools for Arm on GitHub Actions

Warning

The information in this repository is subject to change without notice and does not constitute a commitment by IAR. While it serves as reference model for implementing Continuous Integration with IAR Tools, IAR assumes no responsibility for any errors, omissions, or specific implementations.

Introduction

This repository provides a reasonably simple example to start with, alongside general guidelines on how a CI/CD pipeline can be set up on GitHub Actions, using GitHub-hosted runners to automatically build, test, and deploy a project with the IAR Build Tools for Arm.

Prerequisites

Before you begin, you will need:

• A CI Token for the IAR Build Tools¹.
• A GitHub Account.

In case you need an introduction on how to get started with GitHub, use GitHub Quickstart.

Quickstart

1. Fork or Import this repository.
2. Create a New repository secret for GitHub Actions. Name it IAR_LMS_BEARER_TOKEN, paste your CI Token under Secret and click Add secret

3. Manually run the workflow, or else trigger a new build by commiting and pushing changes to your repository.

GitHub Actions workflow example

On your repository, navigate to the .github/workflows/arm.yml workflow file. This file uses the GitHub-flavored YAML syntax to describe a pipeline containing multiple jobs found in a typical embedded firmware project. This entire pipeline runs in IAR Cloud-ready Containers.

Summary

This repository provided an overview of how simple it is to get started with the IAR Build Tools on GitHub Actions. By harnessing the massive parallization possibilities these modern workflows provide, your development teams can converge efficiently while delivering results with higher quality and reproducibility.

Follow us on GitHub to get updates about examples like this and more.

Issues

For technical support contact IAR Customer Support.

For questions or suggestions related to this example: try the wiki or check earlier issues. If those don't help, create a new issue with detailed information.

Footnotes

1. The use of the IAR Build Tools is subject to the IAR Software License Agreement and requires a valid subscription-based activation token for operation. If you are not yet a subscriber, please contact us for more information. ↩