action #153955
closedcoordination #151816: [epic] Handle openQA fixes and job group setup
Replace header in support images by cleaning of variables
0%
Description
Motivation¶
As far as we keep using the triggering of the maintenance updates builds to run support server images because it is convenient for us, we should just clean properly the settings that we don't use instead of having:
https://openqa.suse.de/admin/job_templates/520?
##########################################################################################
# When publishing the support images for migration test, we don't take the updated #
#repos into account, because we just need the qcow2 images with the latest offical patchs#
##########################################################################################
We need to clean of the settings like BASE_TEST_ISSUES or BASE_TEST_REPOS and we can do it where we set the default for architecture in job group yaml for example.
Acceptance criteria¶
AC1: Settings related with unapproved maintenance updates are not displayed in support server images job group.
Updated by tinawang123 9 months ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by JERiveraMoya 9 months ago
- Description updated (diff)
Optionally in this ticket feel free to investigate the possibility to use the qam-bot and how much effort of recreating setup would be needed or please file another ticket for this idea.
Updated by JERiveraMoya 9 months ago
- Tags changed from qe-yam-feb-sprint to qe-yam-jan-sprint
Updated by tinawang123 9 months ago
Did research about new flavor:
https://gitlab.suse.de/tinawang123/metadata/-/blob/master/bot-ng/sles15sp5.yml?ref_type=heads
Need add new flavor at this file for sles15sp5
With new flavor need set:
aggregate_check_false:
- BASE_TEST_ISSUES
- CONTM_TEST_ISSUES
- DESKTOP_TEST_ISSUES
- LEGACY_TEST_ISSUES
- OS_TEST_ISSUES
- PCM_TEST_ISSUES
- PHUB_TEST_ISSUES
- PYTHON3_TEST_ISSUES
- SCRIPT_TEST_ISSUES
- SDK_TEST_ISSUES
- SERVERAPP_TEST_ISSUES
- WE_TEST_ISSUES Then the trigger command will not add those settings to our job.
Updated by tinawang123 9 months ago
Updated by JERiveraMoya 8 months ago
- Status changed from In Progress to Resolved