Skip to content

[25.12]: Activate luci-app-attendedsysupgrade on buildbot config#8311

Open
hauke wants to merge 3 commits intoopenwrt:openwrt-25.12from
hauke:activate-attendedsysupgrade-in-buildbot-25.12
Open

[25.12]: Activate luci-app-attendedsysupgrade on buildbot config#8311
hauke wants to merge 3 commits intoopenwrt:openwrt-25.12from
hauke:activate-attendedsysupgrade-in-buildbot-25.12

Conversation

@hauke
Copy link
Member

@hauke hauke commented Feb 8, 2026

This will remove the dependency to luci-app-attendedsysupgrade from the luci collections to allow disabling it in custom builds. luci-app-attendedsysupgrade will be activated in buildbot builds.

  • luci-app-attendedsysupgrade: activate in buildbot

    Instead of making the main LuCI packages depend on
    luci-app-attendedsysupgrade, only activate it by default when BUILDBOT
    is seletced.

    This way it is not selected by default in custom builds, but it will be
    automatically selected in builds with CONFIG_BUILDBOT set. Even when
    CONFIG_BUILDBOT is set it is possible to deactivate it.

    This still depends on LuCI, it will only be activated in OpenWrt release
    builds which are build with LuCI and not in OpenWrt main branch builds.

    (cherry picked from commit a0bad5e) (Activate luci-app-attendedsysupgrade and luci based on buildbot config #8303)

  • luci.mk: add support for DEFAULT option

    The default option allows to activate a package by default in Kconfig.
    The user is still able to deactivate the option when it is selected by
    default.

    (cherry picked from commit d6740fd) (Activate luci-app-attendedsysupgrade and luci based on buildbot config #8303)

  • luci-app-attendedsysupgrade: Activate only with LuCI

    Activate luci-app-attendedsysupgrade in buildbots builds only when LuCI
    is also selected. This will prevent it form being activated in master
    buildbot builds.

    (cherry picked from commit b6228b1) (luci-app-attendedsysupgrade: Activate only with LuCI #8312)

@hauke hauke changed the title Activate attendedsysupgrade in buildbot 25.12 [25.12]: Activate luci-app-attendedsysupgrade on buildbot config Feb 8, 2026
@github-actions

This comment has been minimized.

@hauke hauke force-pushed the activate-attendedsysupgrade-in-buildbot-25.12 branch 2 times, most recently from 4aaed08 to 9811d01 Compare February 10, 2026 00:06
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

The default option allows to activate a package by default in Kconfig.
The user is still able to deactivate the option when it is selected by
default.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit d6740fd)
Instead of making the main LuCI packages depend on
luci-app-attendedsysupgrade, only activate it by default when BUILDBOT
is seletced.

This way it is not selected by default in custom builds, but it will be
automatically selected in builds with CONFIG_BUILDBOT set. Even when
CONFIG_BUILDBOT is set it is possible to deactivate it.

This still depends on LuCI, it will only be activated in OpenWrt release
builds which are build with LuCI and not in OpenWrt main branch builds.

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit a0bad5e)
Activate luci-app-attendedsysupgrade in buildbots builds only when LuCI
is also selected. This will prevent it form being activated in master
buildbot builds.

Fixes: a0bad5e ("luci-app-attendedsysupgrade: activate in buildbot")
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
(cherry picked from commit a4117e8)
@hauke hauke force-pushed the activate-attendedsysupgrade-in-buildbot-25.12 branch from 9811d01 to 16d1c51 Compare February 10, 2026 00:10
@github-actions
Copy link

Warning

Some formality checks failed.

Consider (re)reading submissions guidelines.

Failed checks

Issues marked with an ❌ are failing checks.

Commit 16d1c51

  • 🔶 Commit subject length: recommended max 50, required max 60 characters

For more details, see the full job log.

Something broken? Consider providing feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant