buildbot, branch v27

ci: fix missing tag on containers on git tag pushes

2026-01-13T16:49:33Z

Non semver tags like v26 were not included in metadata output, so image pushes only produced sha- tags. Add tag reference metadata so tag pushes publish a matching container tag. ##[warning]v26 is not a valid semver. More info: https://semver.org/ ##[group]Docker tags ghcr.io/openwrt/buildbot/buildmaster-v3.11.8:sha-f2c82f2 Fixes: 93918cc2e225 ("ci: add support for testing PR containers") Signed-off-by: Petr Štetiar

ci: remove cleanup-pr-containers workflow

2026-01-13T16:48:57Z

It needs a bit more time to debug this properly. Signed-off-by: Petr Štetiar

phase2: add support for overriding feeds host

2026-01-12T21:28:00Z

Port the feeds_host_override functionality from phase1 to phase2, allowing phase2 builds to use alternate feed hosts. Signed-off-by: Petr Štetiar

phase1: simplify feeds host override with SDK cleanup

2026-01-12T21:27:58Z

Write to feeds.conf instead of modifying feeds.conf.default in place as the `feeds update` checks feeds.conf first, so no backup/restore dance is needed. Fixes: 057e8adc9d49 ("phase1: add support for overriding feeds host") Signed-off-by: Petr Štetiar

phase1: apply feeds_host_override to main repository URL

2026-01-12T21:27:57Z

When feeds_host_override is configured, also apply it to the main OpenWrt repository URL (repo_url). This fixes git fetch 503 errors when git.openwrt.org is overloaded by redirecting to GitHub mirror. git fetch -f -t https://git.openwrt.org/openwrt/openwrt.git main --progress error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503 fatal: the remote end hung up unexpectedly Signed-off-by: Petr Štetiar

ci: fix workflow_dispatch on PRs by using local context for docker buildx

2026-01-11T21:56:56Z

Without explicit context, docker/build-push-action defaults to fetching from the GitHub repository using github.sha as the ref. For workflow_dispatch events, github.sha points to the default branch (main), not the checked-out PR ref. This caused PR container builds to contain main branch code instead of the PR changes. With `context: .` makes Docker build uses the locally checked-out files from refs/pull/{N}/merge. The issue was identified by inspecting the workflow run logs which showed: docker buildx build ... https://github.com/openwrt/buildbot.git#93918cc2e2257ae8838166d2baad30617295df4e The #93918cc2... ref at the end is the main branch SHA, not the PR merge commit. This is the default behavior when context is not specified - the action uses ${{ github.server_url }}/${{ github.repository }}.git#${{ github.sha }} Signed-off-by: Petr Štetiar

ci: avoid branch tags on workflow_dispatch

2026-01-11T20:52:57Z

Currently workflow_dispatch pushes branch tags, so lets fix it by disabling branch tagging for dispatch runs. Signed-off-by: Petr Štetiar

ci: rename OPENWRT_VERSION to BUILDBOT_CONFIG_SHA

2026-01-11T20:52:45Z

The old name was misleading as it suggested an OpenWrt release version. The variable holds the git SHA of this buildbot config repository, used for quick URL links to the configuration commit. Signed-off-by: Petr Štetiar

ci: add container version tag to BUILDWORKER_DESCRIPTION

2026-01-11T20:52:36Z

Add CONTAINER_TAG build argument to indicate whether the container was built from a tag (v25), PR (pr-73), or branch (main). This makes it easier to identify which version of the container is running. While at it, drop Docker prefix to make it shorter. Signed-off-by: Petr Štetiar

ci: centralize BUILDBOT_VERSION in a shared file

2026-01-11T20:52:12Z

Move the buildbot version from duplicate workflow env blocks to a single .github/buildbot-version file. Signed-off-by: Petr Štetiar