Actions
action #9604
closedmake jobs post to expand TEST and MACHINE variables according to test templates
Start date:
2015-11-18
Due date:
% Done:
0%
Estimated time:
Description
When scheduling one job using client script variables are not processed in any way and just passed to created job. This is unintuitive (isos post expands everything and 'why there are test templates at all?') and produce long commands.
Since we want to schedule only one job we need to avoid parsing job groups, but machines and test case variables can be added automatically.
How to handle backward compatibility?
1) ignore
2) add new API call i.e. /api/v1/jobs2
3) add new variable influencing behaviour of original API call
I'm for 1) or 2). 3) goes directly against REST principle IMO and adds even more confusion.
Actions