647353c929
Merge request changes currently leave all component CRAM jobs dormant. Reviewers cannot see the selected coverage without resolving the matrix themselves, and playing a bucket job cannot combine affected components into one boot. Add per-board changes anchors and six automatic component jobs. Resolve their content from refreshed merge request labels and the diff before any testbed setup. Exit cleanly without DUT cleanup when selection is empty. An automatic selection resolves a union of components that can become a full run, so give these jobs the full-tier 85-minute budget instead of the 40-minute component budget they would otherwise inherit. Add an MR-only report job that prints the complete selection matrix without a build or hardware dependency. Keep all 24 existing bucket jobs unchanged. The automatic template originally extended .cram_component as the later parent after each board template. GitLab's parent precedence therefore reapplied generic .testbed variables over board-specific values. This changed DUT_WAN_INTERFACE on Freedom, Omnia, Haze, Mozart, and Valyrian, and DUT_ARCH_PACKAGES_PATH on OSPv2, Haze, Mozart, and Valyrian. The resulting Freedom failures exposed the wrong interface: ```text 014-firewall-levels.t: grep $DUT_WAN_INTERFACE -> [1] 045-qos.t: grep $DUT_WAN_INTERFACE -> [1] ``` Make .cram_component_auto a standalone overlay because the board parent already supplies the component script and testbed chain. Add a committed guard that resolves all six extends chains and requires each automatic job to preserve its full-bucket sibling's variables. Assisted-by: codex:gpt-5.6-sol References: CI-9 Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> |
||
|---|---|---|
| .devcontainer/ci-env | ||
| .github | ||
| .gitlab | ||
| .testbed | ||
| .vscode | ||
| config | ||
| include | ||
| LICENSES | ||
| package | ||
| profiles | ||
| scripts | ||
| target | ||
| toolchain | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| BSDmakefile | ||
| Config.in | ||
| COPYING | ||
| feeds.conf.default | ||
| Makefile | ||
| README.md | ||
| rules.mk | ||
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0