Skip to content

ci: don't add toolchain explicitly, should be automatic with rust-too… #15

ci: don't add toolchain explicitly, should be automatic with rust-too…

ci: don't add toolchain explicitly, should be automatic with rust-too… #15

Workflow file for this run

name: Build Template
on:
schedule:
- cron: '0 8 * * 1'
push:
branches: ["*"]
paths-ignore:
- "**.md"
pull_request:
branches: ["*"]
paths-ignore:
- "**.md"
env:
CARGO_TERM_COLOR: always
PROJECT_NAME: ch32-blink
jobs:
build:
strategy:
matrix:
mcu_family:
[
ch32l003,
ch32v003,
ch32v103,
ch32v203,
ch32v208,
ch32v303,
ch32v305,
ch32v307,
ch32x033,
ch32x035,
ch641,
]
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: cargo-generate/cargo-generate-action@latest
with:
name: ${{ env.PROJECT_NAME }}
arguments: "--define mcu_family=${{ matrix.mcu_family }}"
# we need to move the generated project to a temp folder, away from the template project
# otherwise `cargo` runs would fail
# see https://github.com/rust-lang/cargo/issues/9922
- name: Move generated project to temp dir
run: |
mv $PROJECT_NAME ${{ runner.temp }}/
- name: Use nightly Rust
run: |
cd ${{ runner.temp }}/$PROJECT_NAME
rustup default nightly
rustup component add rust-src
rustup update
- name: Build
run: |
cd ${{ runner.temp }}/$PROJECT_NAME
cargo build --release