History

Petr Štetiar 587158c13d ci: cdrouter: CDRouter-UPnP-IPv46: enable only tests which are passing We're currently using just a subset of UPnP test cases as being available in CDRouter via PCF-720. We need to increase the QA of UPnP, so lets add complete upnp and upnp-v6 modules, which are known to be working as of today. From the list of available 111 tests in CDRouter version 15.8.1 in both upnp-v6.tcl (60) and upnp.tcl(51) modules we're removing following 30 tests currently known to be not passing: cdrouter_upnp_203, cdrouter_upnp_204, cdrouter_upnp_220, cdrouter_upnp_igd2_203, cdrouter_upnp_igd2_204, cdrouter_upnp_igd2_220, ipv6_upnp_35, ipv6_upnp_36, ipv6_upnp_40, ipv6_upnp_41, ipv6_upnp_45, ipv6_upnp_50, ipv6_upnp_100, ipv6_upnp_203, ipv6_upnp_204, ipv6_upnp_220, ipv6_upnp_igd2_20, ipv6_upnp_igd2_25, ipv6_upnp_igd2_35, ipv6_upnp_igd2_36, ipv6_upnp_igd2_40, ipv6_upnp_igd2_41, ipv6_upnp_igd2_45, ipv6_upnp_igd2_50, ipv6_upnp_igd2_200, ipv6_upnp_igd2_203, ipv6_upnp_igd2_204, ipv6_upnp_igd2_220, ipv6_upnp_igd2_307 So we can regression test UPnP stack in current state and thus improve the QA. Cap the CI job runtime to 60 minutes as currently it seems, that it takes around 53 minutes to complete. References: PCF-720, PPW-336, FEAT-85, FEAT-244 Link: https://support.qacafe.com/cdrouter/knowledge-base/upnp-testing-guide Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org> Co-authored-by: Nikolai Merinov <n.merinov@inango-systems.com>		2025-10-08 20:18:53 +00:00
..
cdrouter	ci: cdrouter: CDRouter-UPnP-IPv46: enable only tests which are passing	2025-10-08 20:18:53 +00:00
certs	ci: ssh-server: add tests for pubkey auth and session features	2025-07-31 10:35:18 +00:00
docker	upnp: extending the cram tests	2025-10-06 20:59:59 +02:00
mockups	ci: sync with current prplos branch state	2025-07-31 10:31:53 +00:00
scripts	ci: cdrouter: start prplMesh in controller mode	2025-07-31 15:29:36 +00:00
testbed	ci: testbed: OSPv2: update flashing procedure to the new flash layout	2025-09-13 06:16:11 +00:00
tests	PROVISORY: ci: cram: mxl25641-hdk-6: 015-platform.t: remove failing sfp test	2025-10-08 11:52:49 +02:00
build.yml	PROVISORY: ci: build: temporarily whitelist MxL ebtables hash to fix CI	2025-10-05 11:30:26 +00:00
cdrouter.yml	ci: fix firmware image copy by using literal block	2025-07-31 15:27:27 +00:00
coverity.yml	ci: coverity: fix build timeout failure by increasing the timeout to 6 hours	2025-07-31 15:23:34 +00:00
docker.yml	ci: fix wasting of runtime testing resources after failed builds	2025-07-31 15:27:24 +00:00
prplmesh.yml	CI: merge smoke stages	2025-07-31 15:29:02 +00:00
README.md	profiles,ci: sunset webui profile	2025-07-31 10:33:15 +00:00
release.yml	PROVISORY: ci: disable support for Mozart board	2025-08-04 10:38:47 +00:00
sdk.yml	ci: ipq807x: fix filenames and references after target rename to qualcommax	2025-07-31 15:25:51 +00:00
testbed.yml	ci: cram: increase timeout with 4 minutes	2025-10-08 10:50:38 +02:00

README.md

Content

This directory contains stuff used on the GitLab CI.

docker

Contains definitions for Docker images.

testbed

Contains definitions for testbed related tests.

scripts

Contains scripts used on GitLab CI.

tests

Contains tests used on GitLab CI.

build.yml

Contains definition of the GitLab CI build test job templates used during build stage. Those templates can then be extended by other GitLab CI jobs in order to keep things DRY.

.build test config

Allows build testing of specific configurations defined in the profiles directory, using scripts/gen_config.py under the hood.

Example usage:

include:
 - local: .gitlab/build.yml

stages:
 - build

build test netgear-rax40 prpl:
  extends: .build test config

Which is going to build test prplOS with netgear-rax40 and prpl profiles.

Description of CI variables:

CI_BUILD_CONFIG_EXTRA - list of additional config options which should be enabled(prefixed with +) or disabled (prefixed with -), for example +BUILD_LOG -SDK would result in CONFIG_BUILD_LOG=y and CONFIG_SDK=y config symbols in .config file.

docker.yml

Provides support for building, tagging and pushing the Docker images to image registry.

For example let's build image foo.

Prerequisites:

Create directory for new Docker image mkdir -p .gitlab/docker/foo
Docker image description $EDITOR .gitlab/docker/foo/Dockefile

Then just put following into .gitlab/docker/foo/gitlab.yml

build Docker image foo:
  extends: .build Docker image

testbed.yml

Provides bits needed for runtime testing on real device using labgrid Python testing framework.

Supported devices:

Netgear RAX40

sdk.yml

Provides support for the OpenWrt SDK utilizing the Docker SDK container under the hood.

.build feed with SDK

Allows compile testing of packages using the SDK.

Example usage, build testing of safec3 package from Intel's feed_opensource_apps feed.

include:
  - remote: https://gitlab.com/prpl-foundation/prplOS/prplos/-/raw/prplos/.gitlab/sdk.yml

build:
  extends: .build feed with SDK
  variables:
    CI_SDK_INSTALL_FEEDS: feed_target_mips
    CI_SDK_BUILD_PACKAGES: safec3

Description of CI variables:

CI_SDK_INSTALL_FEEDS - list of feeds which should be installed prior to building packages.
CI_SDK_BUILD_PACKAGES - list of packages which should be compile tested.
CI_SDK_BUILD_PARALLEL - max number of threads to use for make (defaults to nproc if unset).

.generate SDK package build jobs

Generates sdk-package-jobs.yml with separate build jobs for every package so the builds of those packages can run in parallel. It's supposed to be executed by the child pipeline .execute SDK package build jobs.

.execute SDK package build jobs

It's supposed to execute jobs generated in sdk-package-jobs.yml generated by .generate SDK package build jobs job.