Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add agama staging test #217

Merged
merged 1 commit into from Jun 19, 2023
Merged

Add agama staging test #217

merged 1 commit into from Jun 19, 2023

Conversation

coolgw
Copy link
Contributor

@coolgw coolgw commented Jun 15, 2023

<flavor name="ALP" folder="images/x86_64/agama-live:ALP" distri="alp">
<hdd filemask="agama-live.*-ALP-Build.*iso$"/>
</flavor>
<flavor name="default" folder="images/x86_64/agama-live:default" distri="alp">
Copy link
Contributor

@jknphy jknphy Jun 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the flavor should not be fixed to one architecture, see how it is done in other places:
https://github.com/os-autoinst/openqa-trigger-from-obs/blob/master/xml/obs/SUSE%3AALP%3AMicro.xml#L13
There is some use of /*/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the distri="alp" ? actually Agama is not related with ALP exclusively.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the distri="alp" ? actually Agama is not related with ALP exclusively.

I just following the distri name of https://openqa.opensuse.org/group_overview/96, so which name you prefer it ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@jknphy jknphy Jun 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doesn't look mandatory, we can omit it I guess.

project_pattern="systemsmanagement:Agama:Staging"
dist_path="obspublish-other::openqa/systemsmanagement:Agama:Staging/"
version="agama-0.9"
archs="x86_64 aarch64">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can add the 4 architectures, in some point there will be available.

dist_path="obspublish-other::openqa/systemsmanagement:Agama:Staging/"
version="agama-0.9"
archs="x86_64 aarch64">
<flavor name="ALP" folder="images/x86_64/agama-live:ALP" distri="alp">
Copy link
Contributor

@jknphy jknphy Jun 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't be the flavor names prepended by agama: agama-live:ALP as in OBS to distinguish from other images flavors for other components? for example the cli could have also flavors, https://build.opensuse.org/package/show/systemsmanagement:Agama:Staging/agama-cli
That would help to distinguish them

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't be the flavor names prepended by agama: agama-live:ALP as in OBS to distinguish from other images flavors for other components? for example the cli could have also flavors, https://build.opensuse.org/package/show/systemsmanagement:Agama:Staging/agama-cli That would help to distinguish them

I just use flavor of https://openqa.opensuse.org/group_overview/96, so do you mean we need add prefix for every flavor? Such as:
ALP->agama-live:ALP
defaut->agama-live:default
default-Playwright->agama-live:default-Playwright

Copy link
Contributor

@jknphy jknphy Jun 15, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, but I guess without :, just -, but I'm not sure, we need to look to other examples.

<openQA
project_pattern="systemsmanagement:Agama:Staging"
dist_path="obspublish-other::openqa/systemsmanagement:Agama:Staging/"
version="agama-0.9"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this could have any meaning for a staging project, but I'm not sure what to use ... I guess this is necessary for openQA to configure the mediums, perhaps, agama-staging would be more correct.

@jknphy
Copy link
Contributor

jknphy commented Jun 15, 2023

Once you address that feedback, would be great to run the scripts generated in the O3 server itself to see that everything works before merging, of course along with creating the mediums/configuration in openQA web ui.

@coolgw
Copy link
Contributor Author

coolgw commented Jun 15, 2023

Once you address that feedback, would be great to run the scripts generated in the O3 server itself to see that everything works before merging, of course along with creating the mediums/configuration in openQA web ui.

Do you want create new job group for this staging check or we reuse current job group https://openqa.opensuse.org/group_overview/96?
If you need create new job group, put under which folder?

@jknphy
Copy link
Contributor

jknphy commented Jun 15, 2023

Once you address that feedback, would be great to run the scripts generated in the O3 server itself to see that everything works before merging, of course along with creating the mediums/configuration in openQA web ui.

Do you want create new job group for this staging check or we reuse current job group https://openqa.opensuse.org/group_overview/96? If you need create new job group, put under which folder?

I guess we can reuse existing job group, anyway all that was there was frozen and we need to do some hacks and retrigger it manually so now it might become something better, but yes, should be development because in OBS we would be testing latest commits. Maybe we need to call this staging and have a development one in the future, but I don't think it is the case in O3 for now.

@coolgw
Copy link
Contributor Author

coolgw commented Jun 16, 2023

Once you address that feedback, would be great to run the scripts generated in the O3 server itself to see that everything works before merging, of course along with creating the mediums/configuration in openQA web ui.

Do you want create new job group for this staging check or we reuse current job group https://openqa.opensuse.org/group_overview/96? If you need create new job group, put under which folder?

I guess we can reuse existing job group, anyway all that was there was frozen and we need to do some hacks and retrigger it manually so now it might become something better, but yes, should be development because in OBS we would be testing latest commits. Maybe we need to call this staging and have a development one in the future, but I don't think it is the case in O3 for now.

Create new flavor and manual trigger on O3 setup:
https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-staging&build=2.23&groupid=96
https://openqa.opensuse.org/tests/overview?distri=alp&version=agama-staging&build=2.22&groupid=96

@jknphy
Copy link
Contributor

jknphy commented Jun 16, 2023

@andrii-suse could you please take a look to review?
Just noticed I don't have permission to merge it.
There is some strange circleci issue.

@jknphy
Copy link
Contributor

jknphy commented Jun 18, 2023

@jlausuch could you please give some review here?
I'd like to have permissions to merge here, perhaps you or @andrii-suse could give me those? thanks.

@andrii-suse
Copy link
Collaborator

LGTM, let me know if I need to merge it

@jknphy
Copy link
Contributor

jknphy commented Jun 19, 2023

It is ready to merge, feel free to skip that CI issue as the author will not be available today to rebase.

@andrii-suse andrii-suse merged commit 755124d into os-autoinst:master Jun 19, 2023
4 of 5 checks passed
@jlausuch
Copy link
Contributor

sorry for the late reply (I was OoO). LTGM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants