QA » openQA Project » openQA Tests » qe-yam

Let's do this:
(1) Set CI with custom container created in Rainer's fork
(2) Recover previous Kiwi file contacting with admin to know exact packages installed
(3) Document how to create the personal project in OBS and exact packages needed

Step 2 Update¶

Adrian Schroeter just undeleted the container definition in home:riafarov.
The dockerfile looks like this:

# Defines the tag for OBS and build script builds:
#!BuildTag: tumbleweed:qsf-y-ci

FROM opensuse/tumbleweed
RUN zypper -n in python3-yamllint python3-setuptools openQA-client make

So not much difference from what I temporarily created, maybe the python3-yamllint is missing in the temp image.

Checking of pipelines that were executed with the interim container shows:

scripts/ci_runner_test.sh: line 8: yamllint: command not found

So we need to rebuild the container again with yamllint

Anton recently did some changes to qam-maintenance-yaml to do something here too, perhaps use that one?

szarate wrote:

Anton recently did some changes to qam-maintenance-yaml to do something here too, perhaps use that one?

Should do, has all we need. But still suffers from residing in "home"...

rainerkoenig wrote:

szarate wrote:

Anton recently did some changes to qam-maintenance-yaml to do something here too, perhaps use that one?

Should do, has all we need. But still suffers from residing in "home"...

I ws discussing this with Anton last Wednesday... we can put together our heads to have it in the devel:openQA project in obs.

Let's solve the urgency first (i.e, using anton's project), and then we'll continue providing a base generic image, and everybody else deriving from it, within the same project, maybe or maybe not using your proof of concept :)

Step 3 status update¶

• Moved the image to a safe location. MR to apply the new location
• Wrote a HowTo document to explain, how to move an OBS image to the safe place

This ticket was set to Urgent priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.