telem3-fw/.github/workflows/build.yml

name: Build

on: [push, pull_request]

jobs:
  build:
    runs-on: ubuntu-latest
    container: zephyrprojectrtos/ci:latest
    env:
      CMAKE_PREFIX_PATH: /opt/toolchains
    steps:
      - name: Checkout
        uses: actions/checkout@v2
        with:
          path: example-application

      - name: Initialize
        working-directory: example-application
        run: |
          west init -l .
          west update

      - name: Build firmware
        working-directory: example-application
        run: |
          west build -b custom_plank app

      - name: Twister Tests
        working-directory: example-application
        run: |
          ../zephyr/scripts/twister -G --board-root boards/ --testsuite-root ./tests/

      - name: Archive firmware
        uses: actions/upload-artifact@v2
        with:
          name: firmware
          path: example-application/build/zephyr/zephyr.*
ci: initial CI example CI example using Github Actions Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-04-18 18:57:45 +00:00			`name: Build`

ci: run on pull_request Run CI on push and pull_request. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-05-10 07:53:07 +00:00			`on: [push, pull_request]`
ci: initial CI example CI example using Github Actions Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-04-18 18:57:45 +00:00
			`jobs:`
			`build:`
			`runs-on: ubuntu-latest`
			`container: zephyrprojectrtos/ci:latest`
workflow: add /opt/toolchains to CMAKE_PREFIX_PATH in environment. Fixes: #39270 The latest zephyrprojectrtos/ci no longer sets ZEPHYR_SDK_INSTALL_DIR in the environment and doesn't register the Zephyr-SDK as a CMake package in the CMake package registry. To ensure the the Zephyr SDK can be correctly discovered by find_package(Zephyr-sdk) we add `/opt/toolchains` to the CMAKE_PREFIX_PATH environment variable which is a list containing additional search prefixes for the `find_package()` function. Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no> 2021-10-08 11:11:18 +00:00			`env:`
			`CMAKE_PREFIX_PATH: /opt/toolchains`
ci: initial CI example CI example using Github Actions Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-04-18 18:57:45 +00:00			`steps:`
			`- name: Checkout`
			`uses: actions/checkout@v2`
			`with:`
			`path: example-application`

			`- name: Initialize`
			`working-directory: example-application`
			`run: \|`
			`west init -l .`
			`west update`

			`- name: Build firmware`
			`working-directory: example-application`
			`run: \|`
ci/readme: remove usage of -s legacy option -s/--source is a legacy option. There's a proposal to actually use it for something else in Zephyr now: https://github.com/zephyrproject-rtos/zephyr/pull/40669 Let's update README. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com> 2022-07-01 13:35:04 +00:00			`west build -b custom_plank app`
ci: initial CI example CI example using Github Actions Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-04-18 18:57:45 +00:00
lib: Fix running twister Use integration_platforms and invoke twister properly. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2022-11-19 14:54:27 +00:00			`- name: Twister Tests`
lib: add custom_lib Enhance the example-application repository with a configurable, trivial library example and associated test cases. . This implementation appears to make no assumptions. . This implementation was verified by running the following commands in an example-application workspace and verifying all tests passed. 1. `west build -b native_posix -p always example-application/tests/lib/custom_lib/` 2. `./build/zephyr/zephyr.exe` 3. `west build -b native_posix -p always example-application/tests/lib/custom_lib/ -- -DCONFIG_CUSTOM_LIB_GET_VALUE_DEFAULT=6` 4. `./build/zephyr/zephyr.exe` 5. `zephyr/scripts/twister -T example-application/tests/ \ -p qemu_cortex_m0` 6. `cd zephyr/doc && make clean && make` built cleanly. . Note that `twister` does not follow the `zephyr/module.yml:tests` setting to discover tests in modules, so the testcase-root must be explicitly provided. Fixes #35177 Signed-off-by: Gregory Shue <gregory.shue@legrand.us> 2021-05-21 01:49:09 +00:00			`working-directory: example-application`
			`run: \|`
lib: Fix running twister Use integration_platforms and invoke twister properly. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no> 2022-11-19 14:54:27 +00:00			`../zephyr/scripts/twister -G --board-root boards/ --testsuite-root ./tests/`
lib: add custom_lib Enhance the example-application repository with a configurable, trivial library example and associated test cases. . This implementation appears to make no assumptions. . This implementation was verified by running the following commands in an example-application workspace and verifying all tests passed. 1. `west build -b native_posix -p always example-application/tests/lib/custom_lib/` 2. `./build/zephyr/zephyr.exe` 3. `west build -b native_posix -p always example-application/tests/lib/custom_lib/ -- -DCONFIG_CUSTOM_LIB_GET_VALUE_DEFAULT=6` 4. `./build/zephyr/zephyr.exe` 5. `zephyr/scripts/twister -T example-application/tests/ \ -p qemu_cortex_m0` 6. `cd zephyr/doc && make clean && make` built cleanly. . Note that `twister` does not follow the `zephyr/module.yml:tests` setting to discover tests in modules, so the testcase-root must be explicitly provided. Fixes #35177 Signed-off-by: Gregory Shue <gregory.shue@legrand.us> 2021-05-21 01:49:09 +00:00
ci: initial CI example CI example using Github Actions Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> 2021-04-18 18:57:45 +00:00			`- name: Archive firmware`
			`uses: actions/upload-artifact@v2`
			`with:`
			`name: firmware`
			`path: example-application/build/zephyr/zephyr.*`