Project

General

Profile

Actions
Copy link

action #132692

closed

Support SUMA engineers to setup a SUMA containers test & release pipeline

Added by jlausuch 12 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
ph03nix
Target version:
-
Start date:
2023-07-13
Due date:
% Done:

0%

Estimated time:
Tags:
suma

Description

SUMA engineers, in particular Maurizio Galli, contacted us because they need a pipeline to continuosly update the following SUMA containers:

  • proxy-helm
  • proxy-httpd-image
  • proxy-salt-broker-image
  • proxy-squid-image
  • proxy-ssh-image
  • proxy-tftpd-image

They already have setup the needed projects in IBS so that the container bot can interact with:
CR: https://build.suse.de/project/show/SUSE:SLE-15-SP4:Update:Products:Manager43:Update:CR
Test: https://build.suse.de/project/show/SUSE:SLE-15-SP4:Update:Products:Manager43:Update:CR:ToTest
Release: https://build.suse.de/project/show/SUSE:Containers:SUSE-Manager:4.3

Requirements:

  • The tests can be run on 15-SP4 host
  • Only x86_64
  • 1 single job per container image (similar to Rancher container image)
  • Use 15-SP4 Host HDD_1=SLES-15-SP4-x86_64-containers.qcow2

What SUMA team will do:

  • Provide a MR in the container release bot with a new yaml file suma.yaml to add these images
  • Provide a new test module in os-autoinst-distri-opensuse with minimal coverage, similar to what we do with the Rancher conatiner

What QE-C can help with:

  • Create a new sub job group in Containers parent group called "SUMA Containers" or just "SUMA".
  • Populate that new group with a new yaml file (it could be hosted in
  • Help the SUMA engineers to adapt main_containers.pm to schedule the test module that they will create.
  • Make sure the IBS user we use in the bot has read/write access to the the new CR projects, and ask Autobuild team to provide access.
Actions
Copy link

Also available in: Atom PDF