Skip to content

Latest commit

 

History

History
73 lines (53 loc) · 1.96 KB

README.md

File metadata and controls

73 lines (53 loc) · 1.96 KB

mabg

Test Security check

Marlin auto build generation with github action

why

I use a rapyberry as my personal computer (yes) and compiling Marlin for my ender3 is tiring. So I created this action to help

References

how to

  • Fork Marlin's Repository, make all the changes you need to this fork to make it work on your printer and then create a new action file on .github/workflows/build.yml with this content:
name: Firmware build

on:
  push:
    branches: 2.0.x

jobs:
  build:
    name: Build firmware
    runs-on: ubuntu-latest
    steps:
    -
      name: Check out
      uses: actions/checkout@v2
    -
      name: Marlin auto build generation
      uses: thiago-scherrer/mabg@v1.4
    -
      name: Upload firmware
      uses: actions/upload-artifact@v2
      with:
        name: firmware1.2
        path: .pio/build/STM32F103RC_btt/firmware.bin

I'm using the branch branches: 2.0.x, change it to another if that's your case

If you are using other firmware in your PIO file, change .pio/build/STM32F103RC_btt/firmware.bin it to the version you are using.

  • Push it to your fork and then if everything works out, you can download the compiled binary in your build artifacts:

art

tips

How to keep the Marlin fork updated?

Fetch the updates from the official repository

$ git pull upstream 2.0.x

#Send the updates to your repository.

$git push origin 2.0.x