<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildbot/docker, branch v27</title>
<subtitle>LEDE buildbot configuration</subtitle>
<id>https://git-03.infra.openwrt.org/buildbot/atom?h=v27</id>
<link rel='self' href='https://git-03.infra.openwrt.org/buildbot/atom?h=v27'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/'/>
<updated>2026-01-11T20:52:45Z</updated>
<entry>
<title>ci: rename OPENWRT_VERSION to BUILDBOT_CONFIG_SHA</title>
<updated>2026-01-11T20:52:45Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-01-11T14:13:12Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=61c35ecb418124b342da8db31b8d95e69bb30613'/>
<id>urn:sha1:61c35ecb418124b342da8db31b8d95e69bb30613</id>
<content type='text'>
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 &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>ci: add container version tag to BUILDWORKER_DESCRIPTION</title>
<updated>2026-01-11T20:52:36Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-01-11T13:26:09Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=5cc2a73331ccd72b5d7acf8581cdc2a5fab06863'/>
<id>urn:sha1:5cc2a73331ccd72b5d7acf8581cdc2a5fab06863</id>
<content type='text'>
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 &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>docker: fix Dockerfile deprecation warnings</title>
<updated>2026-01-11T14:30:44Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-01-11T06:30:06Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=c4bcca4c1818dc5235c92d9d5c7b76d12cb3ddef'/>
<id>urn:sha1:c4bcca4c1818dc5235c92d9d5c7b76d12cb3ddef</id>
<content type='text'>
Replace deprecated MAINTAINER instruction with LABEL and update ENV
statements from legacy "ENV key value" format to "ENV key=value" format.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>phase1: add support for overriding feeds host</title>
<updated>2025-12-14T05:09:49Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2025-12-12T21:41:01Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=057e8adc9d49eda73499b5b771cba5df5e8f80d1'/>
<id>urn:sha1:057e8adc9d49eda73499b5b771cba5df5e8f80d1</id>
<content type='text'>
Currently git.openwrt.org is sometimes overloaded, so lets implement a
mechanism to override the source host for feeds.

This introduces a `feeds_host_override` configuration option. When set,
the buildmaster will temporarily modify `feeds.conf.default` to point to
the alternate host (e.g., GitHub) before updating feeds, and restore the
original configuration afterwards.

This is particularly useful when the primary git server is returning 503
errors:

    Updating feed 'packages' from 'https://git.openwrt.org/feed/packages.git' ...
    Cloning into './feeds/packages'...
    fatal: unable to access 'https://git.openwrt.org/feed/packages.git/': The requested URL returned error: 503
    failed.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>docker,worker: install python3-cryptography</title>
<updated>2024-11-25T10:12:20Z</updated>
<author>
<name>Robert Marko</name>
</author>
<published>2024-11-25T09:40:03Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=7f966275500d5cd94cc4b70e0e6bb203d6f569ae'/>
<id>urn:sha1:7f966275500d5cd94cc4b70e0e6bb203d6f569ae</id>
<content type='text'>
Addition of OPTEE support along with STM32 added a requirment on
python3-cryptography and without it buildbots for STM32 will fail with:
Checking 'python3-cryptography'... failed.
Checking 'python3-pyelftools'... ok.
optee-os: Please install the Python3 cryptography module
make[3]: *** [/builder/shared-workdir/build/include/prereq.mk:9: prereq] Error 1

So install python3-cryptography to satisfy it.

Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
Link: https://github.com/openwrt/buildbot/pull/61
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>Allow signing of artifacts with key provided by GPG agent</title>
<updated>2024-11-05T05:07:59Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2024-11-04T20:43:06Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=d014e424f4b440eb4be641e5e408699a63331901'/>
<id>urn:sha1:d014e424f4b440eb4be641e5e408699a63331901</id>
<content type='text'>
In our case the GPG agent serves 0x1D53D1877742E911 key stored on
Nitrokey3 USB dongle. GPG key is bind mounted from the host.

References: https://lists.openwrt.org/pipermail/openwrt-devel/2023-May/041044.html
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>docker,worker: install pyelftools</title>
<updated>2024-11-04T06:35:02Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2024-10-25T09:11:48Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=91f8f2e3763c65a5ba9c9a15768286cfbf7df53f'/>
<id>urn:sha1:91f8f2e3763c65a5ba9c9a15768286cfbf7df53f</id>
<content type='text'>
Without it, errors may appear:

WARNING: Makefile 'package/feeds/telephony/freeswitch/Makefile' has a dependency on 'libpcre', which does not exist
make[2]: Entering directory '/builder/shared-workdir/build/scripts/config'
make[2]: 'conf' is up to date.
make[2]: Leaving directory '/builder/shared-workdir/build/scripts/config'
Checking 'python3-pyelftools'... failed.
Checking 'python3-dev'... ok.
Checking 'python3-setuptools'... ok.
Checking 'swig'... ok.
u-boot: Please install the Python3 elftools module

Fixes: 3ac7d39bd4c3 ("buildworker,buildmaster: bump Debian to version 12")

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
</content>
</entry>
<entry>
<title>Revert "buildworker,buildmaster: bump Debian to version 12"</title>
<updated>2024-11-04T06:12:05Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2024-11-04T06:08:14Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=aab8a542db9576d8ac8121db084f784897742af9'/>
<id>urn:sha1:aab8a542db9576d8ac8121db084f784897742af9</id>
<content type='text'>
This reverts commit 3ac7d39bd4c364d76e78b3ba50c23a68e0b05c0f as it was
decided to stay on Debian 11 for 24.10 release as well.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>buildworker: start: fix broken non TLS setups</title>
<updated>2024-11-04T06:12:04Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2024-10-24T19:55:04Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=dbf5d03807e66f15b1b661a4fac51c6739cad156'/>
<id>urn:sha1:dbf5d03807e66f15b1b661a4fac51c6739cad156</id>
<content type='text'>
Changes in commit 3812ff7bb296 ("buildworker: start: fix worker startup
failure after update") broke non TLS setups. So lets fix it by setting
SSL: only if BUILDWORKER_TLS is set.

Fixes: 3812ff7bb296 ("buildworker: start: fix worker startup failure after update")
Reported-by: Paul Spooren &lt;mail@aparcar.org&gt;
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>buildworker: start: fix leaking BUILDWORKER_TLS env variable</title>
<updated>2024-09-28T17:17:50Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2024-09-28T17:12:55Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/buildbot/commit/?id=213f6de2afc40e27bf6b773b72db0d6104ffd7fb'/>
<id>urn:sha1:213f6de2afc40e27bf6b773b72db0d6104ffd7fb</id>
<content type='text'>
I've noticed leakage of BUILDWORKER_TLS environment variable in build
logs, so lets fix it in a generic way via new
`cleanup_buildworker_env_variables()` by using Bash's parameter
expansion and unset all environment variables starting with BUILDWORKER_
prefix.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
</feed>
