Actions
action #138203
closedcoordination #58184: [saga][epic][use case] full version control awareness within openQA
coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request
[openQA-in-openQA] CI jobs show error but don't fail the CI job as they should *and* openqa_install+publish missing size:M
Start date:
2023-10-18
Due date:
% Done:
0%
Estimated time:
Tags:
Description
https://progress.opensuse.org/issues/138203
Observation¶
{"count":4,"failed":[{"error_message":"The PUBLISH_HDD_1 cannot include \/ in value at \/usr\/share\/openqa\/script\/..\/lib\/OpenQA\/Schema\/ResultSet\/Jobs.pm line 122.\n","job_name":"openqa_install+publish"}],"ids":[3655002,3655003,3655004,3655005],"scheduled_product_id":339600}
maybe that's the reason why openqa_install+publish does not show up?
Acceptance criteria¶
- AC1: error messages returned from the openQA API cause the CI pipeline to abort
- AC2: A default openQA installation using apache is running as part of every pull request to os-autoinst-distri-openQA
Suggestions¶
- Maybe we don't want to call "openqa_install+publish" directly in pull requests as that would take rather long to publish a qcow image and also it might overwrite the production one based on how PUBLISH_HDD_1 is configured. But on the other hand having a qcow file published that one can use directly for investigation and development would be nice. We should check how long it takes with/without publishing and decide what is the good approach for pull request triggered tests and ensure that we do have a default openQA installation using apache is running as part of every pull request to os-autoinst-distri-openQA
- Ensure that in the CI job errors abort the CI with according error as well so that such errors don't go unnoticed (change openqa-cli exit code in case of errors)
Actions