Project

General

Profile

Actions

action #59085

open

Make the YAML editor in Job group more user friendly

Added by Xiaojing_liu over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2019-11-05
Due date:
% Done:

0%

Estimated time:

Description

Users need to write YAML file when editing a job group. It is not friendly. There are some requests about syntax and structure. should we provide a way to make the YAML editor more friendly?


Related issues 1 (1 open0 closed)

Related to openQA Project - action #50675: Commit changes to scheduling YAML to Git repositoryNew2019-04-24

Actions
Actions #1

Updated by okurz over 4 years ago

  • Category set to Feature requests
  • Status changed from New to Blocked
  • Assignee set to okurz

In the subject you write "more visible", in the description it says "more friendly". I assume you mean the latter in general? In any case the current plan is to go with more information stored in VCS itself, e.g. as covered in #50675 so I will mark the ticket as blocked by that one accordingly.

Actions #2

Updated by okurz over 4 years ago

  • Blocked by action #50675: Commit changes to scheduling YAML to Git repository added
Actions #3

Updated by Xiaojing_liu over 4 years ago

okurz wrote:

In the subject you write "more visible", in the description it says "more friendly". I assume you mean the latter in general? In any case the current plan is to go with more information stored in VCS itself, e.g. as covered in #50675 so I will mark the ticket as blocked by that one ayesccordingly.

yes, I mean "more friendly".

Actions #4

Updated by mkittler over 4 years ago

Of course the YAML editor is less easy to use compared to the old one where you just had to select some values from drop down lists. Now you have to C&P from the YAML guide to have at least a base beside products: {} scenarios: {}. It would also be nice to see some real-world examples, e.g. some openSUSE tests I wanted to run locally apparently use a glob star (opensuse-*-Staging-DVD-x86_64 and version: '*') which isn't mentioned in the YAML guide.

Actions #5

Updated by livdywan over 4 years ago

mkittler wrote:

Of course the YAML editor is less easy to use compared to the old one where you just had to select some values from drop down lists. Now you have to C&P from the YAML guide to have at least a base beside products: {} scenarios: {}. It would also be nice to see some real-world examples, e.g. some openSUSE tests I wanted to run locally apparently use a glob star (opensuse-*-Staging-DVD-x86_64 and version: '*') which isn't mentioned in the YAML guide.

Make no mistake, the * has nothing to do with YAML.

Actions #6

Updated by okurz over 4 years ago

  • Blocked by deleted (action #50675: Commit changes to scheduling YAML to Git repository)
Actions #7

Updated by okurz over 4 years ago

  • Related to action #50675: Commit changes to scheduling YAML to Git repository added
Actions #8

Updated by okurz over 4 years ago

  • Subject changed from Make the YAML editor in Job group more visible to Make the YAML editor in Job group more user friendly
  • Status changed from Blocked to New
  • Assignee deleted (okurz)
  • Target version set to future
Actions

Also available in: Atom PDF