Project

General

Profile

action #98823

[tools] Add openQA test for openSUSE jitsi size:M

Added by okurz 11 months ago. Updated 10 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
New test
Target version:
Start date:
2021-09-17
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

As discussed in SUSE QE Tools retro 2021-09-17: meet.opensuse.org broke, maybe due to the special openSUSE branding package. openQA is good at GUI testing so how about we add a test of the jitsi package stack from openSUSE packages to at best prevent faulty packages to be published.

Acceptance criteria

  • AC1: Recurring automatic tests of the packages relevant for meet.opensuse.org exist on o3

Suggestion

  • Ask in #help-jitsi (Slack) where this runs and what the config is
  • https://gitlab.suse.de/azubi/jitsi-opensuse
  • Add new test module to github.com/os-autoinst/os-autoinst-distri-opensuse/ or a new test distri based on github.com/os-autoinst/os-autoinst-distri-example

History

#1 Updated by okurz 11 months ago

  • Description updated (diff)

#2 Updated by cdywan 11 months ago

  • Subject changed from [tools] Add test for openSUSE jitsi to [tools] Add test for openSUSE jitsi size:M
  • Description updated (diff)
  • Status changed from New to Workable

#3 Updated by cdywan 11 months ago

  • Description updated (diff)

#4 Updated by okurz 11 months ago

  • Subject changed from [tools] Add test for openSUSE jitsi size:M to [tools] Add openQA test for openSUSE jitsi size:M
  • Description updated (diff)

#5 Updated by jbaier_cz 11 months ago

  • Assignee set to jbaier_cz

#6 Updated by jbaier_cz 11 months ago

  • Status changed from Workable to In Progress

#7 Updated by cdywan 10 months ago

I seem to recall a test that wasn't fully cleaned up existed from two calls. Can you provide a PR or branch here?

#8 Updated by jbaier_cz 10 months ago

Yes, it is inside a local branch on my development machine: http://polaris.suse.cz/tests/2373. I do not see a reason to open PR yet.

#9 Updated by okurz 10 months ago

Feel very welcome to provide even draft WIP PRs for early feedback

#10 Updated by jbaier_cz 10 months ago

  • Status changed from In Progress to New

After some more investigation, I am afraid I already spent to much time on this low prio ticket. I will pause it for some time and hopefully return in the near future.

I managed to find out following:

  1. There is https://gitlab.suse.de/azubi/jitsi-opensuse with instruction how to install the ecosystem from source and a couple of configuration files. However the instructions there are not entirely accurate and one need to change the configuration slightly to match the instructions. Moreover, the instruction are sometimes not consistent in paths (I assume, the documentation was created after the installation just as a overview of what happened and not updated during maintenance and changes on the jitsi server). As this is the "old" way to install, I do not see a reason to burn more resources to make this work. Current proof of concept is archived inside jitsi branch. It is very hard to try to reverse engineer the setup without accessing the current installation.

  2. As I understood, the openSUSE heroes are trying to create packages to cover the installation and update (instead of doing that from the source), those packages are in OBS however there cannot be installed yet (errors in the packages themselves).

#11 Updated by jbaier_cz 10 months ago

  • Status changed from New to Blocked
  • Assignee deleted (jbaier_cz)

I suggest to wait some time (or spend some time helping) to finish the packaging process and then pick-up this ticket and continue with the process.

#12 Updated by cdywan 10 months ago

  • Status changed from Blocked to Workable

jbaier_cz wrote:

I suggest to wait some time (or spend some time helping) to finish the packaging process and then pick-up this ticket and continue with the process.

Do we have a ticket/bug for the packaging? Otherwise we can't use Blocked here.

#13 Updated by okurz 10 months ago

  • Status changed from Workable to New
  • Target version changed from Ready to future

Well, the idea was to just rely on packages, maybe containers, not needing to replicate the current custom setup. But if there are packages and they currently don't build we can revisit at a later time

Also available in: Atom PDF