pinetime/InfiniTime
1
0
Fork 0
Code Activity
InfiniTime/.github/workflows/main.yml

51 lines
1.6 KiB
YAML
Raw Normal View History

Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
# GitHub Actions Workflow to build FreeRTOS Firmware for PineTime Smart Watch
# See https://lupyuen.github.io/pinetime-rust-mynewt/articles/cloud
Small correction to git URL in documentation files
2021-03-16 00:07:04 +01:00
# Based on https://github.com/JF002/InfiniTime/blob/master/doc/buildAndProgram.md
# and https://github.com/JF002/InfiniTime/blob/master/bootloader/README.md
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
# Name of this Workflow
name: Build PineTime Firmware
# When to run this Workflow...
on:
Run CI on master and develop branch The documentation https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#how-to-submit-a-pull-request- tells us to make pull requests against `develop` branch. Update the CI to run on those pull requests to have a check if the PR breaks something unintentionally.
2021-09-10 23:42:49 +02:00
# Run this Workflow when files are updated (Pushed) in the "master" and "develop" Branch
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
push:
Run CI on master and develop branch The documentation https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#how-to-submit-a-pull-request- tells us to make pull requests against `develop` branch. Update the CI to run on those pull requests to have a check if the PR breaks something unintentionally.
2021-09-10 23:42:49 +02:00
branches: [ master, develop ]
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
Run CI on master and develop branch The documentation https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#how-to-submit-a-pull-request- tells us to make pull requests against `develop` branch. Update the CI to run on those pull requests to have a check if the PR breaks something unintentionally.
2021-09-10 23:42:49 +02:00
# Also run this Workflow when a Pull Request is created or updated in the "master" and "develop" Branch
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
pull_request:
Run CI on master and develop branch The documentation https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#how-to-submit-a-pull-request- tells us to make pull requests against `develop` branch. Update the CI to run on those pull requests to have a check if the PR breaks something unintentionally.
2021-09-10 23:42:49 +02:00
branches: [ master, develop ]
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
# Steps to run for the Workflow
jobs:
build:
runs-on: ubuntu-latest
The main build workflow for GitHub Actions now uses the infinitime-build docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
2022-05-15 10:50:12 +02:00
container:
image: jf002/infinitime-build
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
steps:
The main build workflow for GitHub Actions now uses the infinitime-build docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
2022-05-15 10:50:12 +02:00
- name: Workaround permission issues
run: git config --global --add safe.directory "$GITHUB_WORKSPACE"
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
- name: Checkout source files
uses: actions/checkout@v2
fix Github Action build Firmware
2021-08-14 14:47:00 +02:00
with:
submodules: recursive
The main build workflow for GitHub Actions now uses the infinitime-build docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
2022-05-15 10:50:12 +02:00
- name: Build
shell: bash
env:
SOURCES_DIR: .
run: |
/opt/build.sh all
- name: Upload DFU artifacts
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
uses: actions/upload-artifact@v2
with:
The main build workflow for GitHub Actions now uses the infinitime-build docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
2022-05-15 10:50:12 +02:00
name: InfiniTime DFU file
path: |
./build/output/pinetime-mcuboot-app-dfu-*.zip
- name: Upload MCUBoot image artifacts
Backport Github Actions files from master branch.
2020-09-27 13:10:00 +02:00
uses: actions/upload-artifact@v2
with:
The main build workflow for GitHub Actions now uses the infinitime-build docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format. The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
2022-05-15 10:50:12 +02:00
name: InfiniTime MCUBoot image file
path: |
./build/output/pinetime-mcuboot-app-image-*.bin
Copy permalink