action #152939
Updated by okurz 4 months ago
## Motivation
See
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18182#discussion_r1426859632
in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18182/files/3a35f9b2dae8ea461df44c580a8593393fcf0c99#diff-de0e4ae603aa915aebe97e563c4ffe51dfe10881cc9904c4dfe0c39faebbffd6R25
we need to find out a "latest build", similar as we do in
https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/master/.github/workflows/openqa.yml#L27
which should be easier to get from openQA directly.
Added after QE Tools unblock session: 2024-01-17: We see the main customer value in having a stable API.
## Acceptance criteria
* **AC1:** Both os-autoinst-distri-openQA+os-autoinst-distri-opensuse can use a ~~more simple~~ proper more simple API route to find out the "last finished build"/"last published build" of a product on openQA test results
* **AC2:** The purpose of the new API route is discoverable over at least one other route, e.g. mentioned in the documentation
## Suggestions
* Read and understand both references from os-autoinst-distri-opensuse+openQA
* Add documentation of how the new API route will look like
* Add tests
* Implement
* Replace the code in both os-autoinst-distri-opensuse+openQA
* See https://github.com/os-autoinst/os-autoinst-distri-openQA/blob/80c9212d052ce5406b6020f2c18fbd2e314a4cc6/tests/osautoinst/start_test.pm#L13-L14
* At best create pull requests for both osdo+osda but having the PRs merged is not a hard requirement for this ticket
## Further details
* "osdo" refers to os-autoinst-distri-opensuse
* "osda" refers to os-autoinst-distri-openQA
Back