action #21032
openQA - coordination #162890: [saga][epic] feature discoverability
coordination #162896: [epic] Job triggering on jobless openQA instances
Feature to start new jobs from web interface
0%
Description
Current status¶
if you want run a job in openQA, you need use client script to start up a job in the backend of openqa webui. it is very trouble to switch webui and backend.
want to change¶
can be add a start button after each job test in job group, in order to easy run a job. and also can be added a start all jobs button on the top.
further more¶
I realized there is much more test cases in job group, and much more archs. so I think it will be had a filter to choose which jobs can be run. and a button which can be started those selected jobs.
two parameters need concern¶
that are ISO and BUILD, because there is no such parameters in job group, if we want run every build in openQA, how to handle the new build , old build and milestone build.
further ideas¶
would be nice to also offer retriggering existing tests and asking which options can be changed
Updated by coolo about 7 years ago
- Project changed from openQA Tests to openQA Project
- Subject changed from [tools][openQA][webui][feature]add start button after each test in job group to Feature to start new jobs from web interface
- Category changed from Infrastructure to 124
Updated by okurz about 5 years ago
- Category changed from 124 to Feature requests
Updated by okurz almost 5 years ago
- Related to action #59091: The settings can not be modified when restart a job in web UI added
Updated by okurz over 4 years ago
- Priority changed from Normal to Low
nice idea, hasn't been picked up, implicitly "Low" for us.