<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildbot/phase1, branch v27</title>
<subtitle>LEDE buildbot configuration</subtitle>
<id>https://git.openwrt.org/buildbot/atom?h=v27</id>
<link rel='self' href='https://git.openwrt.org/buildbot/atom?h=v27'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/'/>
<updated>2026-01-12T21:27:58Z</updated>
<entry>
<title>phase1: simplify feeds host override with SDK cleanup</title>
<updated>2026-01-12T21:27:58Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-01-11T06:48:41Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=4bace77250fc67c776f0cd3aa2d6ce4b5ce021bd'/>
<id>urn:sha1:4bace77250fc67c776f0cd3aa2d6ce4b5ce021bd</id>
<content type='text'>
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 &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>phase1: apply feeds_host_override to main repository URL</title>
<updated>2026-01-12T21:27:57Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2026-01-10T19:30:01Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=78343984a6699d6dcaf5e561c6e72887fee5bf3b'/>
<id>urn:sha1:78343984a6699d6dcaf5e561c6e72887fee5bf3b</id>
<content type='text'>
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 &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.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>phase1: fix CONFIG_SIGNED_PACKAGES for apk signing</title>
<updated>2025-12-12T20:49:48Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2025-12-12T20:46:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=a51561bb76cdd9759c693f99527f88a6287532cf'/>
<id>urn:sha1:a51561bb76cdd9759c693f99527f88a6287532cf</id>
<content type='text'>
Currently `CONFIG_SIGNED_PACKAGES` is only enabled when `usign_key` is
configured. However, we also want to enable it when `apk_key` is
configured, as we support signing APK packages as well.

So lets fix it by adding `IsSignedPackagesEnabled` helper which checks
for both keys and updates the .config generation to use it.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>phase1: fix signing steps when only apk_key is defined</title>
<updated>2025-12-11T19:05:20Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2025-12-11T18:13:05Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=b92996c987fa8d09e927be15e5bde3fc405b55b9'/>
<id>urn:sha1:b92996c987fa8d09e927be15e5bde3fc405b55b9</id>
<content type='text'>
Signing steps are currently skipped if only `apk_key` is configured for a
branch, because `IsSignEnabled` only checks for `usign_key` or `gpg_key`.

Fix this by explicitly checking for `apk_key`.

While at it, refactor the signing checks into dedicated helper functions
`IsApkSigningEnabled` and `IsGpgSigningEnabled` for better readability.

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
</content>
</entry>
<entry>
<title>phase1: correctly exclude kmods files from rsync target upload and prune</title>
<updated>2024-11-18T08:08:56Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2024-11-15T15:41:52Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=a75ce026ca9bd5df828e9e51db08f209a716fe82'/>
<id>urn:sha1:a75ce026ca9bd5df828e9e51db08f209a716fe82</id>
<content type='text'>
There is currently a BUG in the --exclude pattern for the targetupload step.
The /kmods/ directory is actually never excluded. This was never notice
as the rsynclist never actually had kmods entry as make checksum step
was done before moving the kmods to the dedicated directory.

This is caused by the fact that with --files-from, not only the /kmods/
directory needs to be excluded but also every content in it, hence the
additional --exclude "/kmods/**" is required to correcly skip the entry
present in rsynclist.

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>pahse1: merge sha256sums with remote kmods entry if present</title>
<updated>2024-11-18T08:08:55Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2024-11-15T14:30:09Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=9f22657ef41bb599558aaeffda451353eaf35199'/>
<id>urn:sha1:9f22657ef41bb599558aaeffda451353eaf35199</id>
<content type='text'>
Add additional logic to merge the sha256sums with the remote kmods entry
(in remote sha256sums) already present.

This is to produce a more consistent sha256sums that actually reflect
what is present in the remote server by including also the sha of the
kmods for each kernel version supported.

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>phase1: remove kmods in target packages if archive is enabled</title>
<updated>2024-11-18T08:08:54Z</updated>
<author>
<name>Daniel Golle</name>
</author>
<published>2024-11-15T14:27:55Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=ec2bd8a07e88f4e251fccb99142bd46c816d62ec'/>
<id>urn:sha1:ec2bd8a07e88f4e251fccb99142bd46c816d62ec</id>
<content type='text'>
OPKG gets confused if kmod packages are present in both, target packages
as well as kernel version specific folder.
Remove them from target packages to make opkg pick the kmods from kmod
archive folder only.

This also affects APK that picks packages from the first entry in the
repository file and doesn't support checking the same package from
multiple entry.

Signed-off-by: Daniel Golle &lt;daniel@makrotopia.org&gt;
[ add --remove-source-files and improve implementation ]
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>phase1: Implement custom step ShellCommandAndSetProperty</title>
<updated>2024-11-18T08:08:53Z</updated>
<author>
<name>Christian Marangi</name>
</author>
<published>2024-11-13T13:30:13Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=b54911df58076545e2be1960dea8f8cb9c03636e'/>
<id>urn:sha1:b54911df58076545e2be1960dea8f8cb9c03636e</id>
<content type='text'>
Implement custom step ShellCommandAndSetProperty, as an extension of
ShellCommand with the addition of setting a bool property that is set
True or False if the shell command succeeded or not.

Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
<entry>
<title>phase1,phase2: GitPoller: fix deprecated API warning for pollinterval</title>
<updated>2024-10-12T08:03:30Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2024-10-12T08:03:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/buildbot/commit/?id=3915bd80cec149897f37530eeaba366aa87e2784'/>
<id>urn:sha1:3915bd80cec149897f37530eeaba366aa87e2784</id>
<content type='text'>
Fixes following warning:

 gitpoller.py:103: buildbot.warnings.DeprecatedApiWarning: [3.11.3 and later] pollinterval has been deprecated: please use pollInterval

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