Project

General

Profile

Actions

Bug #5669

open

Test .deb packages built by our OBS

Added by msuraev 3 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/30/2022
Due date:
% Done:

0%

Spec Reference:

Description

Would be nice to have automated quality checks for our .deb packages similar to nightly tests run for osmo-* projects.

Notable candidates:

This would allow us to catch packaging-related issues early on as well as prevent bitrot (like outdated standards version etc).


Related issues

Related to Cellular Network Infrastructure - Feature #4107: Start systemd services as non-root userStalledmsuraev07/15/2019

Actions
Related to Cellular Network Infrastructure - Feature #2385: validate debian rules/control as part of jenkins build testingResolvedosmith07/21/2017

Actions
Actions #1

Updated by msuraev 3 months ago

  • Related to Feature #4107: Start systemd services as non-root user added
Actions #2

Updated by msuraev 3 months ago

Handy test for "nightly" package builds would be upgrade from latest .deb packages.

Note: debspawn is a nice option for building .deb in isolated environment which does not require complex setup.

Actions #3

Updated by msuraev 3 months ago

  • Related to Feature #2385: validate debian rules/control as part of jenkins build testing added
Actions #4

Updated by osmith 3 months ago

Note that we have some existing tests for the debian and centos packages with the repo-install-test jobs. It tests:
  • packages from the repository can be installed
  • packages conflicting between nightly and latest (so they don't get installed together by accident)
  • osmo-* binaries running and printing a proper version
  • systemd services running properly (also caught conflicting ports between Osmocom applications)
See:

Maybe extend that / maybe add something like lintian in gerrit after #2385?

Actions #5

Updated by msuraev 3 months ago

osmith wrote in #note-4:

  • packages from the repository can be installed

That's subset of what piuparts does.

  • osmo-* binaries running and printing a proper version
  • systemd services running properly (also caught conflicting ports between Osmocom applications)

That seems like smth which can be formalized with autopkgtest. The nice thing about it is that tests are part of the package itself (via debian/tests/ ) which makes it easier to track and maintain.

Actions #6

Updated by osmith 3 months ago

piuparts and autopkgtest look nice! I'm sure there is room for improvement, just pointing out what is already there and that we also test centos packages. Probably best to discuss with Harald if he wants to have this set up.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)