QA » openQA Project

not started, just blocking

How about creating a YAML or JSON file for the requirements and generate cpanfile and rpm from that?

Seems easier especially regarding dependencies per component. Not sure if that is actually possible with the cpanfile format.

Also cpanfile-dump doesn't support module versions, at least cpanfile-dump --help doesn't show anything regarding that.

yes, a generic dependency format looks interesting but if this is the problem then it's a generic problem that I hope was already solved. Do you have experiences from other non-pure perl projects how it is handled there? How about META.json or so? Or does https://metacpan.org/pod/App::mymeta_requires help? Don't have experience in this field.

Sorry, I was already working on something before I went into vacation/holiday.
https://github.com/perlpunk/openQA/tree/deps
https://github.com/perlpunk/openQA/blob/deps/dependencies.yaml

I think it's hard to solve with tools that target only perl, because we currently have different versions for perl and rpm, e.g.
https://github.com/perlpunk/openQA/blob/deps/dependencies.yaml#L72-L73

perl(DBD::Pg):
  perl: '>= 3.007004'
  rpm: '>= 3.7.4'

Draft PR: https://github.com/os-autoinst/openQA/pull/2934

PR https://github.com/os-autoinst/openQA/pull/2934 was merged

As we see the approach useful for openQA we want to consider the same approach for os-autoinst. As discussed with tinita the specific problem of generating rpm requires from cpanfile should be solvable the same in os-autoinst. Open point is where to save the script that helps us generating the dependencies. We see the following options:

1. put the script in os-autoinst and make openQA depend on os-autoinst -> we already depend on os-autoinst, e.g. for the full stack test, so this should be doable
2. copy-paste into both repos – we obviously don't want that :)
3. move the script into a 3rd location and link into both, either as package dependencies or with git submodules/subrepo

With tinita and mkittler and me we decided for option 1, so

• store dependency generation script in os-autoinst
• delete from openQA
• add dependencies.yaml and check in os-autoinst

after that we should be done with this ticket and can continue in #53546

I created https://github.com/os-autoinst/os-autoinst/pull/1401 to move the Dockerfile used for os-autoinst testing from the openQA repo.
After that we need to change the URL here: https://build.opensuse.org/package/view_file/devel:openQA/openqa_dev/_service?expand=1

We are using this package now: https://build.opensuse.org/package/show/devel:openQA/os-autoinst_dev

Now I'll remove the dependencies that were only used by openQA.

PR for removing dependencies: https://github.com/os-autoinst/os-autoinst/pull/1414 (merged)

I disabled the build in https://build.opensuse.org/package/meta/devel:openQA/openqa_dev

PR https://github.com/os-autoinst/os-autoinst/pull/1416 - Dependencies: add tools/update-deps
was merged.

Created https://github.com/os-autoinst/os-autoinst/pull/1420 - Dependencies: Add code to update Dockerfile

Created https://github.com/os-autoinst/os-autoinst/pull/1423 - CI: Install possibly new dependencies