Skip to content

Process_CI: fix broken release-target links (wrong branch + workflow name) #952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
igorpecovnik merged 2 commits into from
Aug 5, 2026
Merged

Process_CI: fix broken release-target links (wrong branch + workflow name) #952

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4faaa4
Process_CI: fix release-target links (wrong branch + wrong workflow n…
igorpecovnik Aug 5, 2026
c2bb98e
Process_CI: fix kernel-description.json CDN link (drop wrong data/ pr…
igorpecovnik Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/Process_CI.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ BOARD_NAME::ENABLE_EXTENSIONS="ext1,ext2"

### Kernel Descriptions for Download Pages

Each kernel branch can include an optional description, automatically generated by the [generate-build-lists workflow](https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-build-lists.yaml) and published to [`kernel-description.json`](https://github.armbian.com/data/release-targets/kernel-description.json).
Each kernel branch can include an optional description, automatically generated by the [generate-build-lists workflow](https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-build-lists.yaml) and published to [`kernel-description.json`](https://github.armbian.com/release-targets/kernel-description.json).

Descriptions are generated from `image-info.json` using template-based categorization (current/edge/legacy/vendor/custom) with version-appropriate naming and platform-specific optimization details.

Expand All @@ -130,7 +130,7 @@ This build workflow is executed manually when making:
**Notes**:

- this process prepares images for release without pushing them to the download pages
- 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!
- you can only generate images that are defined in [targets-release-standard-support.yaml](https://github.com/armbian/armbian.github.io/blob/data/data/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/ci/actions/workflows/build-standard-support.yml) and click
Expand All @@ -156,7 +156,7 @@ Generated images are uploaded to incoming folder [https://fi.mirror.armbian.de/i

### Aditional options

Generates stable images defined in [targets-release-standard-support.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-standard-support.yaml).
Generates stable images defined in [targets-release-standard-support.yaml](https://github.com/armbian/armbian.github.io/blob/data/data/release-targets/targets-release-standard-support.yaml).

We are generating several images for each download / hardware target. They are automatically sorted by sections:

Expand Down Expand Up @@ -187,7 +187,7 @@ This build workflow is executed manually when making:
**Notes**:

- **application images are released 10-15 minutes after build finishes succesfully**
- 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!
- you can only generate images for applications that are defined in [targets-release-apps.yaml](https://github.com/armbian/armbian.github.io/blob/data/data/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/ci/actions/workflows/build-apps.yml) and click
Expand All @@ -212,7 +212,7 @@ Generated images are hosted at GitHub [https://github.com/armbian/distribution/r

### Aditional options

Generates dedicated application images defined in [targets-release-apps.yaml](https://github.com/armbian/armbian.github.io/blob/main/release-targets/targets-release-apps.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 dedicated application images defined in [targets-release-apps.yaml](https://github.com/armbian/armbian.github.io/blob/data/data/release-targets/targets-release-apps.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).

Images generation can be customized:

Expand Down
Loading