History

Iacob Juc fbc039df76 ci: cram: test WPA-Personal-Compatibility interaction with prplMesh prplMesh controller can read configuration from pwhm or from NBAPI. This test covers both input methods. Initial state assumption (based on default configuration) : Controller is reading config from pwhm Operations : Restart prplMesh Enable Priv VAPs Read Security.ModeEnabled - default values Write WPA3-Personal-Compatibility to enabled VAPs - 3 Priv VAPs Check that Controller Reads new values, propagates them to the Agent, and Agent does not overwrite them not-overwrite is a double negation that means agent writes the same value as before. A change would imply that either: 1. Agent incorrectly reported capability - Controller downgraded security mode 2. Controller did not read the configuration and pushed a teardown for the Radiox instead Switch Controller to NBAPI configuration Push WPA3-Personal from NBAPI Push WPA3-Personal-Compatibility from NBAPI Restore Config to default values Increase the testbed timeout. 5min are required to run the test. Closes : PPM-3352 Signed-off-by: Iacob Juc <iacob.juc_ext@softathome.com> Signed-off-by: Houssem Dafdouf <houssem.dafdouf_ext@softathome.com>		2026-02-26 14:20:37 +00:00
..
cdrouter	ci: release,testbed: OSPv2: make firmware filenames UPDK 9.2.3 compliant	2026-01-29 10:46:42 +00:00
certs	ci: ssh-server: add tests for pubkey auth and session features	2025-07-31 10:35:18 +00:00
docker	ci: cram: new test development for tr181-periodicfileupload	2026-02-19 15:11:44 +01:00
mockups	ci: sync with current prplos branch state	2025-07-31 10:31:53 +00:00
scripts	ci: testbed,cdrouter: improve error visibility with colored logging	2025-11-07 06:00:20 +00:00
testbed	ci: release,testbed: OSPv2: make firmware filenames UPDK 9.2.3 compliant	2026-01-29 10:46:42 +00:00
tests	ci: cram: test WPA-Personal-Compatibility interaction with prplMesh	2026-02-26 14:20:37 +00:00
blackduck.yml	ci: blackduck: Add tar.gz archiving of BlackDuck scan output	2025-11-21 12:35:44 +01:00
build.yml	ci: build: remove duplicate CI_BUILD_PROFILE export from script section	2025-11-28 13:26:22 +00:00
cdrouter.yml	ci: testbed,cdrouter: improve error visibility with colored logging	2025-11-07 06:00:20 +00:00
coverity.yml	coverity.yml: use environment variable for INCLUDE_DIAGNOSTICS value	2025-11-17 13:20:36 +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: prplMesh: unbuffer python stdout	2025-10-15 10:06:24 +00:00
README.md	profiles,ci: sunset webui profile	2025-07-31 10:33:15 +00:00
release.yml	ci: release,testbed: OSPv2: make firmware filenames UPDK 9.2.3 compliant	2026-01-29 10:46:42 +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: test WPA-Personal-Compatibility interaction with prplMesh	2026-02-26 14:20:37 +00: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.