action #59085

Make the YAML editor in Job group more user friendly

Added by Xiaojing_liu 4 months ago. Updated 3 months ago.

Status:NewStart date:05/11/2019
Priority:LowDue date:
Assignee:-% Done:

0%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

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

Related to openQA Project - action #50675: Commit changes to scheduling YAML to Git repository New 24/04/2019 29/02/2020

History

#1 Updated by okurz 4 months 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.

#2 Updated by okurz 4 months ago

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

#3 Updated by Xiaojing_liu 3 months 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".

#4 Updated by mkittler 3 months 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.

#5 Updated by cdywan 3 months 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.

#6 Updated by okurz 3 months ago

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

#7 Updated by okurz 3 months ago

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

#8 Updated by okurz 3 months 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

Also available in: Atom PDF