diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 484c6cc..da246e0 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -1,4 +1,4 @@ -name: Build +name: Monthly build on: workflow_dispatch: schedule: @@ -9,7 +9,7 @@ jobs: runs-on: ubuntu-latest steps: - name: Checkout - uses: actions/checkout@v2 + uses: actions/checkout@v3 - name: Get time id: time uses: nanzm/get-time-action@v1.1 @@ -24,6 +24,7 @@ jobs: token: ${{ secrets.GITHUB_TOKEN }} target_commitish: main draft: false + prerelease: true outputs: release_id: ${{ steps.release.outputs.id }} build: @@ -31,25 +32,44 @@ jobs: needs: prepare_release strategy: matrix: - BOARD: [radxa-e25] - DISTRO: [debos] - FLAVOR: [debian, ubuntu] + boards: [radxa-e25] + build_systems: [debos, rbuild] + distros: [debian, ubuntu] + flavors: [cli] + exclude: + - build_systems: debos + distros: debian + flavors: cli + - build_systems: debos + distros: ubuntu + flavors: kde steps: - name: Checkout uses: actions/checkout@v2 - name: Upload Armbian image uses: radxa/armbian-compile-action@main - if: matrix.DISTRO == 'armbian' + if: matrix.build_systems == 'armbian' with: - board: ${{ matrix.BOARD }} - flavor: ${{ matrix.FLAVOR }} + board: ${{ matrix.boards }} + distro: ${{ matrix.distros }} + flavor: ${{ matrix.flavors }} release-id: ${{ needs.prepare_release.outputs.release_id }} github-token: ${{ secrets.GITHUB_TOKEN }} - name: Upload debos-radxa image uses: radxa/debos-build-action@main - if: matrix.DISTRO == 'debos' + if: matrix.build_systems == 'debos' + with: + board: ${{ matrix.boards }} + distro: ${{ matrix.distros }} + flavor: ${{ matrix.flavors }} + release-id: ${{ needs.prepare_release.outputs.release_id }} + github-token: ${{ secrets.GITHUB_TOKEN }} + - name: Upload rbuild image + uses: radxa-repo/rbuild@main + if: matrix.build_systems == 'rbuild' with: - board: ${{ matrix.BOARD }} - flavor: ${{ matrix.FLAVOR }} + board: ${{ matrix.boards }} + distro: ${{ matrix.distros }} + flavor: ${{ matrix.flavors }} release-id: ${{ needs.prepare_release.outputs.release_id }} github-token: ${{ secrets.GITHUB_TOKEN }} diff --git a/README.md b/README.md index 2af4fd9..3da0c39 100644 --- a/README.md +++ b/README.md @@ -1,17 +1,30 @@ -# Radxa E25 -[![iso_build](https://github.com/radxa-build/radxa-e25/workflows/Build/badge.svg)](https://github.com/radxa-build/radxa-e25/actions/workflows/build.yml) +# Radxa E25 Dual 2.5Gb Ethernet Carrier Board +[![Build](https://github.com/radxa-build/radxa-e25/workflows/Build/badge.svg)](https://github.com/radxa-build/radxa-e25/actions/workflows/build.yml) ## What is this? -A collection of auto-generated images for Radxa E25. +This repo is the central location for Radxa-built system images for Radxa E25 Dual 2.5Gb Ethernet Carrier Board. -* Radxa debos image will have name started with the board name. +Not all images are officially supported by Radxa. Some of them are only provided as-is with no warranty. Please read below for detailed explanations. -## Where can I download the image? +## What images are provided? -Built images are uploaded to [GitHub Releases](https://github.com/radxa-build/radxa-e25/releases/latest). +Currently the following images are provided: +* Radxa [`debos-radxa`](https://github.com/radxa/debos-radxa) images (currently supported) +* Radxa [`rbuild`](https://github.com/radxa-repo/rbuild) images (currently testing) + +`debos-radxa` images contain the build time in the file name, while `rbuild` images have a fixed file name across releases. They have similar file name format as `rbuild` is intended to replace `debos-radxa`. Once we deem `rbuild` is production-ready we will cease to produce `debos-radxa` images to avoid confusion. + +## Is there any other options? + +Please visit [our Wiki](https://wiki.radxa.com/Rock3/downloads) for more download options. + +## Where can I download the Radxa image? + +Every month new images are [built](https://github.com/radxa-build/radxa-e25/actions/workflows/build.yml) and [published](https://github.com/radxa-build/radxa-e25/releases) as pre-releases, which serve as release candidates (RC). Radxa will periodically select an RC for additional testing, and once it passes those tests, promote it as an officially supported release. This is why you are always recommended to use [the latest release](https://github.com/radxa-build/radxa-e25/releases/latest). ## Help! Something doesn't work! -Please first take a look at [our Wiki](https://wiki.radxa.com/Home) which covers the most basics. -Should you have any additional question, please visit [our forum](https://rock.sh/go) or [our Discord](https://rock.sh/go), and we are willing to help. +For other questions, please first take a look at [our Wiki](https://wiki.radxa.com/Rock3/CM/CM3I/E25), which covers the most basic usages. + +Should you have any additional questions, please visit [our forum](https://forum.radxa.com/) or [our Discord](https://rock.sh/go), and we are willing to help.