Hi,

osmo-gsm-tester jobs are set up different because the nodes expected to run them are quite specialized: they need a different set of dependencies and HW attached to it than a regular "osmocom builder".

In osmo-gsm-tester, we build sysroots of different osmocom projects which will later be packaged into a "trial" used by osmo-gsm-tester main unit to run the tests. This part of building the osmocom project sysroots (osmo-gsm-tester-builder.yml) can be done by a normal osmocom jenkins build node, and it is actually done by them.

The osmo-gsm-tester_runner.yml require to be run in a "osmo-gsm-tester main unit" node, with different dependencies and HW attached as explained above.

What I would do:
* Add a new "master-osmo-gsm-tester" job together either together with other "master-" jobs or inside osmo-gsm-tester-builder.yml, because those nodes should more or less have the same dependencies. This "master-osmo-gsm-tester" needs to only build + publish the pdf to the FTP server. A new script can be created for that in osmo-gsm-tester.git/contrib/. Feel free to depend on osmo-ci or copy whatever is needed as you see makes sense.

* Extend osmo-gsm-tester_gerrit job (which calls osmo-ci.git/contrib/jobs/osmo-gsm-tester_run-gerrit.sh) to also build the manuals in osmo-gsm-tester.git but no publish them. Since this job is run in an "osmo-gsm-tester main unit" node, that means you mayu need to update the ansible files in osmo-ci.git to install required dependencies onto those nodes. See osmo-ci.git/ansible/roles/gsm-tester/.



As a reminder, this is the job actually running the full set of tests in osmo-gsm-tester main unit (Prod setup):
https://jenkins.osmocom.org/jenkins/view/osmo-gsm-tester/job/osmo-gsm-tester_run-prod/

--
- Pau Espin Pedrol <[email protected]>         http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte

Reply via email to