-
Notifications
You must be signed in to change notification settings - Fork 269
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
Migrate first steps in qam-yast_self_update+15 to libyui REST #15143
Migrate first steps in qam-yast_self_update+15 to libyui REST #15143
Conversation
a7992cc
to
e8a3b62
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main point missing is adding the updates, for that we still don't have libyui-rest module available and I have some plan to do it, so we can postpone, only the few modules at the beginning are needed.
we would need verification for SP3 and SP4, including uefi flavor.
Additionally we would need a PR for setup this test suite in Development group:
https://gitlab.suse.de/qa-maintenance/qam-openqa-yml/-/blob/master/JobGroups/yast/maint_updates_devel.yml
0afc43c
to
cf27035
Compare
created merge request on gitlab |
14f4b8f
to
8c00b32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commit message and the PR title should follow some basic rules, it should start by capital letter and should be some sentences with no commas, something meaningful like:
Migrate first steps in qam-yast_self_update+15 to libyui REST
The reason for that is that some contributors use git log
to check the commits and should be easy to understand the changes and the scope of those from there as well, not only checking gitlab. Some references:
https://commit.style/
https://cbea.ms/git-commit/
we usually gather all this info in the first comment of the PR, so we have all the links available at the top. |
c32ddbf
to
2864f66
Compare
2864f66
to
4496451
Compare
bcc2dfe
to
4d038c4
Compare
4d038c4
to
dd01c0d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking really good, some feedback.
bb0ecdf
to
e18d2fa
Compare
e18d2fa
to
5988302
Compare
tests/installation/module_registration/register_extensions_and_modules.pm
Outdated
Show resolved
Hide resolved
f27bc38
to
918a6d4
Compare
918a6d4
to
d7ab6d5
Compare
tests/installation/module_registration/register_extensions_and_modules.pm
Show resolved
Hide resolved
tests/installation/module_registration/register_extensions_and_modules.pm
Show resolved
Hide resolved
Perform testing with libyui REST API since the version of the product where it is available, SP3 and above. Related ticket: https://progress.opensuse.org/issues/112574
d7ab6d5
to
1f969d5
Compare
Good job! |
Apply libyui-REST for yast qam self-update install tests. Intended to replace
qam-yast-self-update.yaml
only on >= 15SP3