Project

General

Profile

action #50675

openQA Tests - coordination #15132: [saga][epic] Better structure of test plans in main.pm

coordination #44360: [epic] Parameterize test suites within job groups

Commit changes to scheduling YAML to Git repository

Added by mkittler over 2 years ago. Updated about 1 year ago.

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

0%

Estimated time:
Difficulty:

Description

The PR for the YAML import (https://github.com/os-autoinst/openQA/pull/2044) comes already with a basic web UI. So far changes are applied to openQA's database but the goal is to manage the YAML within Git. Therefore the web UI should also push the changes to a Git repository, similar to how the needle editor works.

tasks

  1. Make the YAML import route commit the changes also via Git. It should be configurable like the Git commit feature of the needle editor.
  2. Setup a Git repository for OSD and o3 and configure those instances.

Related issues

Related to openQA Tests - action #57536: [functional][y] implement autodeployment of the job group settings to osdResolved2019-09-30

Related to openQA Project - action #59085: Make the YAML editor in Job group more user friendlyNew2019-11-05

History

#2 Updated by cdywan over 2 years ago

As per today's weekly we decided that support for a Git backend will be optional and not mandatory for using job template YAML in production.

#3 Updated by okurz over 2 years ago

  • Category set to Feature requests

#4 Updated by coolo over 2 years ago

  • Target version set to future

We come to it - eventually

#5 Updated by mkittler about 2 years ago

Note that it would be conceivable to get rid of the editor in the web UI and commit changes only via Git. However, the editor has a nice preview feature and validation. Besides, it is possibly more convenient to use for casual users.

So it would be nice if the editor would still be able to create commits itself. With the needle editor we use the same approach but it sometimes leads to problems (e.g. messes up Git repo). Maybe we can improve that by pushing the commit only to a newly created branch. Then we can just redirect the user to the "Create PR" page of GitHub/GitLab for that branch.

#6 Updated by mkittler about 2 years ago

  • Related to action #57536: [functional][y] implement autodeployment of the job group settings to osd added

#7 Updated by coolo about 2 years ago

That sounds like a good compromise actually.

#8 Updated by okurz about 2 years ago

  • Blocks action #59085: Make the YAML editor in Job group more user friendly added

#9 Updated by okurz about 2 years ago

  • Due date set to 2020-02-29

setting due-date to a later date to prevent reminders in the parent ticket as other, resolved tickets have their due dates passed by now.

#10 Updated by okurz about 2 years ago

  • Blocks deleted (action #59085: Make the YAML editor in Job group more user friendly)

#11 Updated by okurz about 2 years ago

  • Related to action #59085: Make the YAML editor in Job group more user friendly added

#12 Updated by okurz about 1 year ago

  • Priority changed from Normal to Low

#13 Updated by okurz about 1 year ago

  • Due date deleted (2020-02-29)

Also available in: Atom PDF