maple/prplos
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
66,018 Commits 1 Branch 0 Tags 238 MiB
C 55.7%
Makefile 17.6%
Perl 7.8%
Shell 6.9%
Roff 6.1%
Other 5.7%
3c56f4f028
Go to file
Petr Štetiar 3c56f4f028 ci: cram: lint component manifest in pipelines 
The component manifest lint currently runs only during local validation.
Merge requests get no feedback when new tests silently enter the prplos
remainder.

Add a non-DUT manifest coverage job to every pipeline. Fetch an MR base
when needed and pass it to the lint. Newly-in-remainder warnings then
appear in job output.

Give the job explicit rules: a job without rules keeps the legacy
branches-and-tags default and is never created in merge-request
pipelines, the exact place the diff-base comparison exists for. Skip
scheduled pipelines, which carry no cram work.

Use the digest-pinned testbed v1.3.0 image for Python, YAML, and git. The
MR diff-base comparison requires runtime git for cat-file, fetch, and the
lint script's child processes.

The image runs as the testbed user while the runner checkout has a
different owner. Git otherwise rejects the checkout before lint starts:

```text
fatal: detected dubious ownership in repository at
'/builds/prpl-foundation/prplos/prplos'
```

Pass a safe.directory override for CI_PROJECT_DIR through Git's inherited
configuration environment. Print the selected MR diff base so the
comparison path remains visible in job evidence. Add no hardware runner
tags or build dependencies.

Assisted-by: codex:gpt-5
Assisted-by: claude:fable-5
References: CI-7
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
2026-08-19 10:14:27 +00:00
.devcontainer/ci-env devcontainer: Add development environment for gihub codespace 2023-10-30 23:34:26 +01:00
.github CI: remove labeler workflow and enable webhook-based labeling 2026-08-18 11:40:42 +01:00
.gitlab ci: cram: lint component manifest in pipelines 2026-08-19 10:14:27 +00:00
.testbed ci: testbed: labgrid: bump OSPv2 login_timeout for lcm_data reformat 2026-07-02 07:30:07 +02:00
.vscode meta: VS Code: add "Git: Always Sign Off" setting 2024-10-03 17:18:51 +02:00
config mold: dont allow on MacOS 2026-07-09 10:57:30 +01:00
include fix: Restore the changes made for PCF-2730: restore version branch defaults 2026-08-18 16:25:44 +01:00
LICENSES
package OpenWrt v24.10.8: adjust config defaults 2026-08-18 11:40:42 +01:00
profiles profiles: prpl_core.yml: feed_prplos: tr069-manager: Fix missing documentation artifacts in build-documentation job 2026-08-19 10:58:14 +01:00
scripts scripts/ext-tools.sh: set all prebuilt tool files to same timestamp 2026-08-18 11:40:40 +01:00
target airoha: update PCS driver with new upstream version 2026-08-18 11:40:42 +01:00
toolchain toolchain: gcc: fix include memory against GCC 16 2026-08-18 11:40:42 +01:00
tools tools: ccache: disable build testing 2026-08-18 11:40:42 +01:00
.gitattributes
.gitignore ci: cram: add DHCPv4 Force option cram tests 2026-06-02 17:59:31 +01:00
.gitlab-ci.yml ci: cram: add component split jobs behind CRAM_COMPONENTS 2026-08-19 10:14:27 +00:00
BSDmakefile
Config.in build: scripts/config - update to kconfig-v5.14 2022-02-19 13:10:01 +01:00
COPYING
feeds.conf.default OpenWrt v24.10.8: adjust config defaults 2026-08-18 11:40:42 +01:00
Makefile build,base-files: propagate prplOS version into build artifacts 2025-07-31 15:18:10 +00:00
README.md README: replace "MacOSX" with "macOS" 2024-04-01 18:46:30 +02:00
rules.mk build: do not set CCACHE_COMPILERCHECK 2026-08-18 11:40:40 +01:00

README.md

OpenWrt logo

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

  1. Run ./scripts/feeds update -a to obtain all the latest package definitions defined in feeds.conf / feeds.conf.default

  2. Run ./scripts/feeds install -a to install symlinks for all obtained packages into package/feeds/

  3. Run make menuconfig to select your preferred configuration for the toolchain, target system & firmware packages.

  4. Run make to 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 #openwrt on oftc.net.

Developer Community

License

OpenWrt is licensed under GPL-2.0