.. | ||
build-board-list.yml | ||
build-train.yml | ||
forked-helper.yml | ||
kernel-security-analysis-pr.yml | ||
labeler.yml | ||
lint-scripts-pr.yml | ||
open-jira-ticket.yml | ||
README.md | ||
rebase.yml | ||
scorecard.yml |
Runners requirements
- big (6-16 cores, 64Gb SSD, 16Gb memory, 2Gb swap)
- small (4 cores, 64Gb SSD, 8Gb memory, 2Gb swap)
Preparation
Adding x86 runner to your Jammy VM (check here if any changes):
$ mkdir actions-runner
$ cd actions-runner
$ curl -o actions-runner-linux-x64-2.294.0.tar.gz -L https://github.com/actions/runner/releases/download/v2.294.0/actions-runner-linux-x64-2.294.0.tar.gz
$ tar xzf ./actions-runner-linux-x64-2.294.0.tar.gz
Configuration
Once asked, tag your runner accordingly:
- small
- big
- arm64
Start the configuration experience
$ ./config.sh --url https://github.com/armbian --token XXXXXXXXXXXXXXXXXXXXXXXXXXX
You need to get a valid token from our DevOps team to proceed.
Create startup scripts
sudo ./svc.sh install # install
sudo ./svc.sh start # start
sudo ./svc.sh status # check
Use workflows in forked repositories
forked-helper.yml
workflow helper can help to run custom workflows on the forked repositories.
- Set
ARMBIAN_SELF_DISPATCH_TOKEN
secret on your repository withsecurity_events
permissions. - Helper will dispatch
repository_dispatch
eventarmbian
onpush
,release
,deployment
,pull_request
andworkflow_dispatch
events. All needed event details you can find inclient_payload
property of the event. - Create empty default branch in forked repository
- Create workflow with
repository_dispatch
in default branch. - Run any need actions in this workflow.
Workflow example:
name: Test Armbian dispatch
on:
repository_dispatch:
types: ["armbian"]
jobs:
show-dispatch:
name: Show dispatch event details
runs-on: ubuntu-latest
steps:
- uses: hmarr/debug-action@v2