mirror of https://github.com/armbian/build.git
Bumps [actions/checkout](https://github.com/actions/checkout) from 5 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/v5...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| adjust-maintainers.yml | ||
| clean-workflow-logs.yml | ||
| forked-helper.yml | ||
| issue-welcome-first-time.yml | ||
| labels-from-yml.yml | ||
| merge-announce.yml | ||
| open-jira-ticket.yml | ||
| pr-announce.yml | ||
| pr-auto-labeler.yml | ||
| pr-build-artifacts.yml | ||
| pr-kernel-security-analysis.yml | ||
| pr-label-on-approved.yml | ||
| pr-lint-scripts.yml | ||
| pr-review-listener.yml | ||
| pr-welcome-first-time.yml | ||
| rewrite-kernel-configs.yml | ||
| scorecard.yml | ||
| update-board-list.yml | ||
| update-tools.yml | ||
README.md
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