From 549e9c072d153df337b4da6a1a1a4fdd04b7a0a4 Mon Sep 17 00:00:00 2001 From: Igor Pecovnik Date: Mon, 3 Aug 2026 00:30:35 +0200 Subject: [PATCH 1/2] Process_CI: move automation references from armbian/os to armbian/ci The build pipeline moved from armbian/os (deprecated) to armbian/ci, and repository/download-page automation now lives in armbian.github.io. Update all workflow/badge links accordingly: - standard-support/apps/all/nightly -> armbian/ci build-*.yml workflows - targets-all-not-eos.yaml -> armbian/ci/userpatches/ - repository-update -> armbian.github.io infrastructure-repository-update.yml - webindex refresh -> armbian.github.io data-update-download-index.yml - drop stable.json/nightly.json (versioning now driven by GitHub releases) - remove the Full distro test builds section (no armbian/ci equivalent) - add a deprecation note for armbian/os Signed-off-by: Igor Pecovnik --- docs/Process_CI.md | 40 ++++++++++++++-------------------------- 1 file changed, 14 insertions(+), 26 deletions(-) diff --git a/docs/Process_CI.md b/docs/Process_CI.md index d4289133d..2524fc615 100644 --- a/docs/Process_CI.md +++ b/docs/Process_CI.md @@ -1,6 +1,9 @@ # Automation for developers and maintainers -Core automation for generating images for release are held at +Core automation for generating images for release is held at (the reusable build pipeline and its track wrappers). Repository, download-page and mirror automation lives at [`armbian/armbian.github.io`](https://github.com/armbian/armbian.github.io). + +???+ Warning + The old [`armbian/os`](https://github.com/armbian/os) repository is deprecated and no longer used for build automation. All workflows have moved to `armbian/ci` (builds) and `armbian.github.io` (publishing/repository). ???+ Note For monitoring Armbian action scripts status and execution details, visit [https://actions.armbian.com/](https://actions.armbian.com/) @@ -116,7 +119,7 @@ Unfortunatelly this part does not have testing at PR stage. ???+ Info Manual executing permissions are tied to [release manager role](/Process_Contribute/#release-manager). -[![Build Standard Support Images](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-standard-support.yml/badge.svg)](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-standard-support.yml) +[![Build Standard Support Images](https://github.com/armbian/ci/actions/workflows/build-standard-support.yml/badge.svg)](https://github.com/armbian/ci/actions/workflows/build-standard-support.yml) This build workflow is executed manually when making: @@ -130,7 +133,7 @@ This build workflow is executed manually when making: - you can only generate images that are defined in [targets-release-standard-support.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-standard-support.yaml) build lists! - images generation workflows are compiled and are pretty much the same, just with different defaults -### 1. Open [workflow](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-standard-support.yml) and click +### 1. Open [workflow](https://github.com/armbian/ci/actions/workflows/build-standard-support.yml) and click ![Run Workflow](images/run-workflow.png) @@ -141,10 +144,7 @@ This build workflow is executed manually when making: **Bump version**: Select if you want to trigger system wide version bump. **Version override**: Set version under which you want to release images. -Images versions are stored in JSON files: - -- https://github.com/armbian/os/blob/main/stable.json -- https://github.com/armbian/os/blob/main/nightly.json +Versioning is driven by the GitHub releases on the target repository — there is no version file to edit. Stable builds require an explicit `versionOverride` (e.g. `26.8.0`); nightly builds pick the newest `-trunk.N` release and bump `N`. ### 3. Run workflow @@ -176,7 +176,7 @@ Images generation can be customized: ## Prepare application images for release (release manager) -[![Build Dedicated Application Images](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-apps.yml/badge.svg)](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-apps.yml) +[![Build Dedicated Application Images](https://github.com/armbian/ci/actions/workflows/build-apps.yml/badge.svg)](https://github.com/armbian/ci/actions/workflows/build-apps.yml) This build workflow is executed manually when making: @@ -190,7 +190,7 @@ This build workflow is executed manually when making: - you can only generate images for applications that are defined in [targets-release-apps.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-apps.yaml) build lists! - images generation workflows are compiled and are pretty much the same, just with different defaults -### 1. Open [workflow](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-apps.yml) and click +### 1. Open [workflow](https://github.com/armbian/ci/actions/workflows/build-apps.yml) and click ![Run Workflow](images/run-workflow.png) @@ -231,7 +231,7 @@ This pulls packages from build framework OCI cache located at GitHub and from [v - `apt.armbian.com` (only new packages are added) - `beta.armbian.com` (whole repository is recreated from scratch) -### 1. Open [workflow](https://github.com/armbian/os/actions/workflows/repository-update.yml) and click +### 1. Open [workflow](https://github.com/armbian/armbian.github.io/actions/workflows/infrastructure-repository-update.yml) and click ![Run Workflow](images/run-workflow.png) @@ -252,34 +252,22 @@ is selected. ## Build all artifacts (cronjob) -[![Build All Artifacts](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-all.yml/badge.svg)](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-all.yml) +[![Build All Artifacts](https://github.com/armbian/ci/actions/workflows/build-all.yml/badge.svg)](https://github.com/armbian/ci/actions/workflows/build-all.yml) -Generates all build artifacts cache for targets defined in [targets-all-not-eos.yaml](https://github.com/armbian/os/blob/main/userpatches/targets-all-not-eos.yaml). This build job runs **every 8 hours** and can also be run manually when needed. +Generates all build artifacts cache for targets defined in [targets-all-not-eos.yaml](https://github.com/armbian/ci/blob/main/userpatches/targets-all-not-eos.yaml). This build job runs on a schedule and can also be run manually when needed. This build job **needs to be successfully completed** in order to proceed generating any OS images! ## Build Rolling Release Images (cronjob) -[![Build Nightly Images](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-nightly.yml/badge.svg)](https://github.com/armbian/os/actions/workflows/complete-artifact-matrix-nightly.yml) +[![Build Nightly Images](https://github.com/armbian/ci/actions/workflows/build-nightly.yml/badge.svg)](https://github.com/armbian/ci/actions/workflows/build-nightly.yml) Generates all nightly (Rolling Release) images defined in [targets-release-nightly.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-nightly.yaml). This file is automatically generated from `image-info.json` by the [generate-targets workflow](https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-targets.yaml). -This build job runs every day at 9 a.m. UTC and can also be run manually when needed. Download pages are refreshed [automatically](https://github.com/armbian/os/actions/workflows/webindex-update.yml) after successful build. +This build job runs every night and can also be run manually when needed. Download pages are refreshed [automatically](https://github.com/armbian/armbian.github.io/actions/workflows/data-update-download-index.yml) after successful build. ![Build](images/rolling-releases.png) -## Full distro test builds (cronjob/release manager) - -[![Build Nightly Images](https://github.com/armbian/os/actions/workflows/full-distro-build-and-test.yml/badge.svg)](https://github.com/armbian/os/actions/workflows/full-distro-build-and-test.yml) - -Generates all supported build combinations (minimal, cli, desktops) for x86 architecture to check package level changes inconsistency and dependencies. - -Options: - -- Framework build branch - - **main** - - testing_branch (string) - ## Build all artifacts (admin/PR) Generates artifacts at Pull Requests code. Build starts when label of Pull Request is set to "Build". Requires administration privileges. From e7035022822114c2950d626f84f43848a0ccf2f4 Mon Sep 17 00:00:00 2001 From: Igor Pecovnik Date: Mon, 3 Aug 2026 17:58:41 +0200 Subject: [PATCH 2/2] Process_CI: correct versioning, artifact-gate, and nightly target/generator refs Address the coderabbit review (all verified against armbian/ci and armbian/armbian.github.io): - Versioning: stable builds do NOT require versionOverride - build-standard- support/build-all-stable default it to '' and complete-artifact-matrix reuses the newest X.Y.Z release; the override only seeds a release or picks a different version. - Build All Artifacts is not a hard prerequisite for image generation: image workflows build their own artifacts in the same run; Build All only pre-populates the shared cache. - Nightly targets link: the file lives on the data branch under data/release-targets/, and the generator is generate-build-lists.yaml (generate-targets.yaml does not exist). Signed-off-by: Igor Pecovnik --- docs/Process_CI.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Process_CI.md b/docs/Process_CI.md index 2524fc615..e70338ec8 100644 --- a/docs/Process_CI.md +++ b/docs/Process_CI.md @@ -144,7 +144,7 @@ This build workflow is executed manually when making: **Bump version**: Select if you want to trigger system wide version bump. **Version override**: Set version under which you want to release images. -Versioning is driven by the GitHub releases on the target repository — there is no version file to edit. Stable builds require an explicit `versionOverride` (e.g. `26.8.0`); nightly builds pick the newest `-trunk.N` release and bump `N`. +Versioning is driven by the GitHub releases on the target repository — there is no version file to edit. Stable builds reuse the newest `X.Y.Z` release unless `versionOverride` is set; use the override to seed a release or select a different version. Nightly builds pick the newest `-trunk.N` release and bump `N`. ### 3. Run workflow @@ -256,13 +256,13 @@ is selected. Generates all build artifacts cache for targets defined in [targets-all-not-eos.yaml](https://github.com/armbian/ci/blob/main/userpatches/targets-all-not-eos.yaml). This build job runs on a schedule and can also be run manually when needed. -This build job **needs to be successfully completed** in order to proceed generating any OS images! +This build job pre-populates the artifact cache used by image builds. Image workflows also build their required artifacts in the same workflow run. ## Build Rolling Release Images (cronjob) [![Build Nightly Images](https://github.com/armbian/ci/actions/workflows/build-nightly.yml/badge.svg)](https://github.com/armbian/ci/actions/workflows/build-nightly.yml) -Generates all nightly (Rolling Release) images defined in [targets-release-nightly.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-nightly.yaml). This file is automatically generated from `image-info.json` by the [generate-targets workflow](https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-targets.yaml). +Generates all nightly (Rolling Release) images defined in [targets-release-nightly.yaml](https://github.com/armbian/armbian.github.io/blob/data/data/release-targets/targets-release-nightly.yaml). This file is automatically generated from `image-info.json` by the [generate-build-lists workflow](https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-build-lists.yaml). This build job runs every night and can also be run manually when needed. Download pages are refreshed [automatically](https://github.com/armbian/armbian.github.io/actions/workflows/data-update-download-index.yml) after successful build.