Actions
action #71809
closedcoordination #103962: [saga][epic] Easy multi-machine handling: MM-tests as first-class citizens
coordination #103965: [epic] Easy triggering of multi-machine tests, similar as for single-machine tests
Enable multi-machine jobs trigger without "isos post"
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2020-09-24
Due date:
% Done:
0%
Estimated time:
Description
In case of single job you have two options to trigger it :
1.) isos post ( requires certain setup on target openQA )
2.) jobs post ( can be done on any "random" openQA server because all variables are not calculated from flavors , job groups , machines etc. but coming with a call )
In case of multi-machine job you have only first option .
We need to find a way to trigger multi-machine jobs on target openQA host without require certain setup on it
Updated by asmorodskyi over 4 years ago
- Status changed from New to In Progress
- Assignee set to asmorodskyi
Updated by asmorodskyi over 4 years ago
- Related to coordination #58184: [saga][epic][use case] full version control awareness within openQA added
Updated by okurz about 4 years ago
- Project changed from openQA Tests (public) to openQA Project (public)
- Category set to Feature requests
- Target version set to future
Updated by asmorodskyi about 4 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
asmorodskyi)
Updated by okurz about 3 years ago
- Related to action #103425: Ratio of multi-machine tests alerting with ratio_mm_failed 5.280 size:M added
Updated by okurz about 3 years ago
- Related to action #95783: Provide support for multi-machine scenarios handled by openqa-investigate size:M added
Updated by okurz about 3 years ago
- Related to deleted (coordination #58184: [saga][epic][use case] full version control awareness within openQA)
Updated by mkittler almost 3 years ago
- Status changed from Workable to Feedback
- Assignee set to mkittler
Actions