prplos/.gitlab
Petr Štetiar 7198bfc91a
ci: testbed: increase test runtime from 48min to 53min
In the past few days we've added several test cases:

 * 2026-02-09 257ee69bb7 ci: cram: add test for bSTAMLD feature
 * 2026-02-09 e4bad077fe ci: cram: freedom: pwhm: test GetEHTOperations APIs
 * 2026-02-09 0254e003b1 ci: cram: freedom: split script 101-mlo.t
 * 2026-02-09 0dca07a46e ci: cram: add cram test for pwhm native APMLD feature
 * 2026-02-06 61af18f6dd ci: cram: add lcm-syslog unpriv tests
 * 2026-02-06 b60f186712 ci: cram: add cleanup lcm syslog tests
 * 2026-02-06 ed3cccc049 ci: cram: adapt tests with introduction of LCM syslog
 * 2026-02-06 cf253a0a06 ci: cram: add test 038-lcm-syslog.t
 * 2026-02-06 22a7748057 ci: cram: obuspa.t: add Device.UPnP.Discovery.
 * 2026-02-06 9512863824 ci: cram: obuspa: add Device.UPnPDiscovery

Which obviously impacts the test runtime, so we've started seeing
various test timeouts:

 .gitlab/tests/cram/wnc-freedom/105-pwhm-wpa3-cm.t: passed
 .gitlab/tests/cram/wnc-freedom/110-prplmesh-dataelements.t: timeout: sending signal TERM to command ‘python3’

So lets fix it by extending the test runtime timeout by 5 minutes.

Closes: PPW-1490
Link: https://gitlab.com/prpl-foundation/prplos/prplos/-/jobs/13002415393#L205
Signed-off-by: Petr Štetiar <petr.stetiar@prplfoundation.org>
2026-02-13 07:44:55 +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: blackduck: move blackduck to separate job 2025-11-21 12:33:10 +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: add test for bSTAMLD feature 2026-02-09 15:20:25 +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: testbed: increase test runtime from 48min to 53min 2026-02-13 07:44:55 +00:00

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.