All Projects → arduino → compile-sketches

arduino / compile-sketches

Licence: other
GitHub Actions action that checks whether Arduino sketches compile and produces a report of data from the compilations

Programming Languages

python
139335 projects - #7 most used programming language
shell
77523 projects

Projects that are alternatives of or similar to compile-sketches

overview
Automate your workflows with GitHub actions for MATLAB.
Stars: ✭ 40 (+14.29%)
Mutual labels:  continuous-integration, github-actions
github-act-runner
act as self-hosted runner
Stars: ✭ 68 (+94.29%)
Mutual labels:  continuous-integration, github-actions
drupal9ci
One-line installers for implementing Continuous Integration in Drupal 9
Stars: ✭ 137 (+291.43%)
Mutual labels:  continuous-integration, github-actions
setup-scheme
Github Actions CI / CD setup for Scheme
Stars: ✭ 13 (-62.86%)
Mutual labels:  continuous-integration, github-actions
cross-platform-python-gui
A fork-ready base for your new GUI application. Uses CI to automatically build executables for Linux (AppImage), Windows (exe), and MacOS (dmg)
Stars: ✭ 53 (+51.43%)
Mutual labels:  continuous-integration, github-actions
arduino-lint-action
GitHub Actions action to check Arduino projects for problems
Stars: ✭ 20 (-42.86%)
Mutual labels:  continuous-integration, github-actions
demo-ci
Aula prática sobre servidores de Integração Contínua
Stars: ✭ 15 (-57.14%)
Mutual labels:  continuous-integration, github-actions
xray-action
... a GitHub action to import test results into "Xray" - A complete Test Management tool for Jira.
Stars: ✭ 16 (-54.29%)
Mutual labels:  continuous-integration, github-actions
django-security-check
Helps you continuously monitor and fix common security vulnerabilities in your Django application.
Stars: ✭ 69 (+97.14%)
Mutual labels:  continuous-integration, github-actions
Android-CICD
This repo demonstrates how to work on CI/CD for Mobile Apps 📱 using Github Actions 💊 + Firebase Distribution 🎉
Stars: ✭ 37 (+5.71%)
Mutual labels:  continuous-integration, github-actions
github-create-release-action
Github Action that create Github Release automatically
Stars: ✭ 28 (-20%)
Mutual labels:  continuous-integration, github-actions
Setup Php
GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
Stars: ✭ 1,945 (+5457.14%)
Mutual labels:  continuous-integration, github-actions
arduino-lint
Tool to check for problems with Arduino projects
Stars: ✭ 63 (+80%)
Mutual labels:  continuous-integration, tooling-team
lychee-action
Github action to check for broken links in Markdown, HTML, and text files using lychee, a fast link checker written in Rust.
Stars: ✭ 89 (+154.29%)
Mutual labels:  continuous-integration, github-actions
bump-everywhere
🚀 Automate versioning, changelog creation, README updates and GitHub releases using GitHub Actions,npm, docker or bash.
Stars: ✭ 24 (-31.43%)
Mutual labels:  continuous-integration, github-actions
qodana-action
⚙️ Scan your Java, Kotlin, PHP, Python, JavaScript, TypeScript projects at GitHub with Qodana
Stars: ✭ 112 (+220%)
Mutual labels:  continuous-integration, github-actions
noise-php
A starter-kit for your PHP project.
Stars: ✭ 52 (+48.57%)
Mutual labels:  continuous-integration, github-actions
link-snitch
GitHub Action to scan your site for broken links so you can fix them 🔗
Stars: ✭ 50 (+42.86%)
Mutual labels:  continuous-integration, github-actions
cake-build
Demonstrates a basic build of a .NET NuGet package using https://cakebuild.net/
Stars: ✭ 22 (-37.14%)
Mutual labels:  continuous-integration, github-actions
Cml
♾️ CML - Continuous Machine Learning | CI/CD for ML
Stars: ✭ 2,843 (+8022.86%)
Mutual labels:  continuous-integration, github-actions

arduino/compile-sketches action

Tests Lint Spell Check codecov

This action checks whether Arduino sketches compile and produces a report of data from the compilations.

Table of contents

Inputs

cli-version

The version of Arduino CLI to use.

Default: "latest"

fqbn

The fully qualified board name to use when compiling.

Default: "arduino:avr:uno"

If the board is from one of the platforms provided by Arduino's default package index, the board's platform dependency will be automatically detected and the latest version installed. For boards of platforms not in the default package index, previous versions, or other platform sources, the platform dependency must be defined via the platforms input.

platforms

YAML-format list of platform dependencies to install.

Default: The board's dependency will be automatically determined from the fqbn input and the latest version of that platform will be installed via Boards Manager.

If a platform dependency from a non-Boards Manager source of the same name as another Boards Manager source platform dependency is defined, they will both be installed, with the non-Boards Manager dependency overwriting the Boards Manager platform installation. This permits testing against a non-release version of a platform while using Boards Manager to install the platform's tools dependencies. Example:

platforms: |
  # Install the latest release of Arduino SAMD Boards and its toolchain via Boards Manager
  - name: "arduino:samd"
  # Install the platform from the root of the repository, replacing the BM installed platform
  - source-path: "."
    name: "arduino:samd"

Supported platform sources:

Boards Manager

Keys:

  • name - (required) platform name in the form of VENDOR:ARCHITECTURE (e.g., arduino:avr).
  • version - version of the platform to install.
    • Default: the latest version.
  • source-url - Boards Manager URL of the platform.
    • Default: Arduino's package index, which allows installation of all official platforms.
Local path

Keys:

  • source-path - (required) path to install as a platform. Relative paths are assumed to be relative to the root of the repository.
  • name - (required) platform name in the form of VENDOR:ARCHITECTURE (e.g., arduino:avr).
Repository

Keys:

  • source-url - (required) URL to clone the repository from. It must start with git:// or end with .git.
  • name - (required) platform name in the form of VENDOR:ARCHITECTURE (e.g., arduino:avr).
  • version - Git ref of the repository to checkout. The special version name latest will cause the latest tag to be used.
    • Default: the repository is checked out to the tip of the default branch.
  • source-path - path to install as a platform. Paths are relative to the root of the repository.
    • Default: root of the repository.
Archive download

Keys:

  • source-url - (required) download URL for the archive (e.g., https://github.com/arduino/ArduinoCore-avr/archive/master.zip).
  • name - (required) platform name in the form of VENDOR:ARCHITECTURE (e.g., arduino:avr).
  • source-path - path to install as a platform. Paths are relative to the root folder of the archive, or the root of the archive if it has no root folder.
    • Default: root folder of the archive.

libraries

YAML-format list of library dependencies to install.

Default: "- source-path: ./" This causes the repository to be installed as a library. If there are no library dependencies and you want to override the default, set the libraries input to an empty list (- libraries: '-').

Libraries are installed under the Arduino user folder at ~/Arduino/libraries.

Note: when the deprecated space-separated list format of this input is used, the repository under test will always be installed as a library.

Supported library sources:

Library Manager

Keys:

  • name - (required) name of the library, as defined in the name field of its library.properties metadata file.
  • version - version of the library to install.
    • Default: the latest version.

Notes:

  • The library will be installed to a folder matching its name, but with any spaces replaced by _.
  • If the library's author defined dependencies, those libraries will be installed automatically.
Local path

Keys:

  • source-path - (required) path to install as a library. Relative paths are assumed to be relative to the root of the repository.
  • destination-name - folder name to install the library to.
    • Default: the folder will be named according to the source repository or subfolder name.
Repository

Keys:

  • source-url - (required) URL to clone the repository from. It must start with git:// or end with .git.
  • version - Git ref of the repository to checkout. The special version name latest will cause the latest tag to be used.
    • Default: the tip of the default branch.
  • source-path - path to install as a library. Paths are relative to the root of the repository.
    • Default: root of the repository.
  • destination-name - folder name to install the library to.
    • Default: named according to the source repository or subfolder name.
Archive download

Keys:

  • source-url - (required) download URL for the archive (e.g., https://github.com/arduino-libraries/Servo/archive/master.zip).
  • source-path - path to install as a library. Paths are relative to the root folder of the archive, or the root of the archive if it has no root folder.
    • Default: root folder of the archive.
  • destination-name - folder name to install the library to.
    • Default: named according to the source archive or subfolder name.

sketch-paths

YAML-format list of paths containing sketches to compile. These paths will be searched recursively.

Default: "- examples"

cli-compile-flags

YAML-format list of flags to add to the Arduino CLI command used to compile the sketches. For the available flags, see the Arduino CLI command reference.

Default: ""

verbose

Set to true to show verbose output in the log.

Default: false

sketches-report-path

Path in which to save a JSON formatted file containing data from the sketch compilations. Should be used only to store reports. Relative paths are relative to GITHUB_WORKSPACE. The folder will be created if it doesn't already exist.

This report is used by the arduino/report-size-deltas and arduino/report-size-trends actions.

Default: "sketches-reports"

github-token

GitHub access token used to get information from the GitHub API. Only needed for private repositories with enable-deltas-report set to true. It will be convenient to use ${{ secrets.GITHUB_TOKEN }}.

Default: ""

enable-deltas-report

Set to true to cause the action to determine the change in memory usage and compiler warnings of the compiled sketches.

If the workflow is triggered by a pull_request event, the comparison is between the pull request branch and the tip of the pull request's base branch.

If the workflow is triggered by a push event, the comparison is between the pushed commit and its immediate parent.

The deltas will be displayed in the GitHub Actions build log.

This report may be used with the arduino/report-size-deltas action.

Default: false

How it works

The sketch is first compiled with the repository in $GITHUB_WORKSPACE at the state it was at before the action's step. Data from the compilation is recorded in the sketches report. Next, a [git checkout] to the Git ref used as the base of the comparison is done and the compilation + data recording process repeated. The delta is the change in the data between the two compilations.

Dependencies defined via the libraries or platforms inputs are installed via symlinks, meaning dependencies from local paths under $GITHUB_WORKSPACE reflect the deltas checkouts even though they are installed outside $GITHUB_WORKSPACE.

enable-warnings-report

Set to true to cause the action to record the compiler warning count for each sketch compilation in the sketches report.

Default: false

Example usage

- uses: arduino/compile-sketches@v1
  with:
    fqbn: 'arduino:avr:uno'
    libraries: |
      - name: Servo
      - name: Stepper
        version: 1.1.3
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].