action #105160: Automatic triggering of Windows Image Update test runs - Containers and images - openSUSE Project Management Tool

Actions

Copy link

action #105160

closed

Automatic triggering of Windows Image Update test runs

Added by jlausuch almost 3 years ago. Updated 2 months ago.

Status:

Resolved

Priority:

Low

Assignee:

Target version:

Start date:

2022-01-20

Due date:

% Done:

Estimated time:

Tags:

WSL

Description

The way to update the Windows image is implemented, https://progress.opensuse.org/issues/60341
However, we can't override the target qcow PUBLISH_HDD_1 with the same name as the origin qcow2 HDD_1, so we need some logic that detects that a new image has been created and then replace the files in OSD and O3.

Maybe this can be done with a cronjob in gitlab, we would need to set up ssh access from gitlab to both places:
openqa.suse.de
openqa.opensuse.org

Acceptance Criteria¶

Create pipeline (gitlab?) to update the Windows image

Related issues 4 (0 open — 4 closed)

Actions

Copy link

Updated by jlausuch almost 3 years ago

Related to action #60341: [qac][research][wsl] update windows image in openqa added

Actions

Copy link

Updated by jlausuch almost 3 years ago

Related to action #99978: upgrade windows 10 image in openQA added

Actions

Copy link

Updated by ilausuch over 2 years ago

Description updated (diff)

Actions

Copy link

Updated by pherranz over 2 years ago

Status changed from Workable to In Progress
Assignee set to pherranz

Actions

Copy link

Updated by pherranz over 2 years ago

The Windows version does not update as often, so maybe as a complementary action to updating the ISO, there should be a job to run the Windows Update task periodically before running any other WSL tests.

Actions

Copy link

Updated by pherranz over 2 years ago

Related to action #117577: Create a job to periodically run Windows Update added

Actions

Copy link

Updated by pherranz about 2 years ago

Status changed from In Progress to Blocked

Blocked also due to #117577

Actions

Copy link

Updated by pherranz about 2 years ago

With every new version Microsoft is changing very small details, like new pictures, different typos or new installation screens. It has taken me about 2-3 working days to adapt the current 21H2 jobs to the new installation of 22H2.

Actions

Copy link

Updated by pherranz about 2 years ago

Related to action #121033: [WSL] Unattended Windows install added

Actions

Copy link

#10

Updated by pherranz about 2 years ago

Status changed from Blocked to Workable
Assignee deleted (~~pherranz~~)

The ISO is hard to get automatically from the Microsoft site as there's need to fulfill a form previous to get the download link.
I've read somewhere that an ISO image can be downloaded from the Azure platform, by having the right access and privileges, this should be researched in the near future.

Actions

Copy link

#11