https://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092022-08-30T08:10:18ZOpen Source Mobile CommunicationsCellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=247882022-08-30T08:10:18Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-7 priority-3 priority-high3 parent" href="/issues/4107">Feature #4107</a>: Start systemd services as non-root user</i> added</li></ul> Cellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=247892022-08-30T08:24:27Zmsuraev
<ul></ul><p>Handy test for "nightly" package builds would be upgrade from latest .deb packages.</p>
<p>Note: debspawn is a nice option for building .deb in isolated environment which does not require complex setup.</p> Cellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=249462022-09-21T12:04:25Zmsuraev
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-3 priority-2 priority-default closed" href="/issues/2385">Feature #2385</a>: validate debian rules/control as part of jenkins build testing</i> added</li></ul> Cellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=249472022-09-21T12:25:56Zosmith
<ul></ul>Note that we have some existing tests for the debian and centos packages with the repo-install-test jobs. It tests:
<ul>
<li>packages from the repository can be installed</li>
<li>packages conflicting between nightly and latest (so they don't get installed together by accident)</li>
<li>osmo-* binaries running and printing a proper version</li>
<li>systemd services running properly (also caught conflicting ports between Osmocom applications)</li>
</ul>
See:
<ul>
<li><a class="external" href="https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian11/">https://jenkins.osmocom.org/jenkins/job/Osmocom-repo-install-debian11/</a></li>
<li><a class="external" href="https://gitea.osmocom.org/osmocom/osmo-ci/src/commit/4a0b42cc4f1ef0d79dea4ae5618213c3e3e4963f/scripts/repo-install-test/run-inside-docker.sh#L415-L434">https://gitea.osmocom.org/osmocom/osmo-ci/src/commit/4a0b42cc4f1ef0d79dea4ae5618213c3e3e4963f/scripts/repo-install-test/run-inside-docker.sh#L415-L434</a></li>
</ul>
<p>Maybe extend that / maybe add something like lintian in gerrit after <a class="issue tracker-2 status-3 priority-2 priority-default closed" title="Feature: validate debian rules/control as part of jenkins build testing (Resolved)" href="https://projects.osmocom.org/issues/2385">#2385</a>?</p> Cellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=249482022-09-21T12:41:40Zmsuraev
<ul></ul><p>osmith wrote in <a href="#note-4">#note-4</a>:</p>
<blockquote>
<ul>
<li>packages from the repository can be installed</li>
</ul>
</blockquote>
<p>That's subset of what piuparts does.</p>
<blockquote>
<ul>
<li>osmo-* binaries running and printing a proper version</li>
<li>systemd services running properly (also caught conflicting ports between Osmocom applications)</li>
</ul>
</blockquote>
<p>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.</p> Cellular Network Infrastructure - Bug #5669: Test .deb packages built by our OBShttps://projects.osmocom.org/issues/5669?journal_id=249492022-09-21T13:03:12Zosmith
<ul></ul><p>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.</p>