mirror of
https://github.com/armbian/build.git
synced 2026-01-06 09:58:46 -08:00
Make all workflow names consistent and action-oriented: - Use action verb first (Announce, Auto-label, Build, Check, Clean, Help, Label, Lint, Listen, Rewrite, Scan, Sync, Welcome) - Keep names concise and descriptive - Remove unnecessary details from the name Changes: - Analyze kernel security (was: Kernel Hardening Analysis) - Announce merge (was: Announce PR merge to Discord) - Announce PR (was: Announce PR on Discord for review) - Auto-label PR (was: Automatic Pull Request Labeling) - Build PR artifacts (was: Generate Artifacts on PR if...) - Check PR assets (was: Check new board assets exist...) - Clean workflow logs (was: Clean Workflow Logs) - Sync Jira (was: Jira Sync) - Help forks (was: Forked Helper) - Label PR on approval (was: PR review labeler) - Lint scripts (was: Lint on Scripts) - Listen PR review (was: PR review listener) - Rewrite kernel configs (was: Rewrite kernel configs - same) - Scan security (was: Scorecards Security Scan) - Sync board list (was: Update Board Lists) - Sync labels (was: Sync Labels from YAML) - Sync maintainers (was: Sync maintainers status) - Sync tools (was: Update Tools in Scripts) - Welcome first-time contributor (was: Welcome first-time issue contributor) - Welcome first-time PR contributor (was: same - kept as is)
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.
- Create a fine-grained Personal Access Token (PAT) with the
reposcope and store it as a secret. It needs the following permissions on the target repositories:contents: read & writemetadata: read only (automatically selected when selecting the contents permission)
- Create a secret named
ARMBIAN_SELF_DISPATCH_TOKENon your repository withsecurity_eventspermissions. To do this, head to your forked repository, go toSettingson the top bar, selectSecrets and variablesand thenActions. From here you can create a new repository secret.Name:ARMBIAN_SELF_DISPATCH_TOKENSecret: Paste your fine-grained Personal Access Token that you created in step 1 here
- Helper will dispatch
repository_dispatcheventarmbianonpush,release,deployment,pull_requestandworkflow_dispatchevents. All needed event details you can find inclient_payloadproperty of the event. - Create empty default branch in forked repository
- Create workflow with
repository_dispatchin 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