Project

General

Profile

Actions

coordination #129313

open

coordination #127031: [saga][epic] openQA for SUSE customers

[epic] openQA on ALP

Added by okurz over 1 year ago. Updated 4 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA - future
Start date:
2023-05-15
Due date:
% Done:

80%

Estimated time:
(Total: 0.00 h)

Description

Current situation

https://build.suse.de/project/show/home:okurz:BCI shows an attempt to build a SUSE BCI based openQA container. So far dependencies can not be fully resolved.
https://build.suse.de/project/show/home:okurz:BCI:deps links the at least necessary dependencies from SUSE:Factory:Head and more dependencies are needed and can be deduced from the "unresolvable" messages.

Open Points

https://build.suse.de/project/show/home:okurz:BCI:deps shows currently 105 packages and still many dependencies missing for a full development environment. So I see the following open points:

  1. We have multiple containers in the scope of openQA on https://registry.opensuse.org/cgi-bin/cooverview?srch_term=project%3D%5Edevel%3AopenQA+container%3D.* . What would be the benefit to submit to https://build.opensuse.org/project/show/SUSE:ALP:Workloads for containers that can already be pulled from a path like registry.opensuse.org/devel/openqa/containers/openqa-single-instance:latest?
  2. What's the benefit to build based on SLE BCI instead of openSUSE Tumbleweed?
  3. If we should continue with the approach as visible in https://build.suse.de/project/show/home:okurz:BCI:deps, what is the way forward? Brute-force submit all those missing dependencies into SLE until all openQA derived packages can be built?

Subtasks 1 (0 open1 closed)

action #129316: [spike][timeboxed:20h] openQA container on ALPResolvedokurz2023-05-15

Actions
Actions

Also available in: Atom PDF