Project

General

Profile

Actions

action #42647

open

Proper integration of kernel tests into openSUSE Tumbleweed release process, e.g. teach ttm to support multiple job groups

Added by okurz over 5 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2018-08-31
Due date:
% Done:

0%

Estimated time:

Description

Motivation

The "totest-manager", in short ttm, is an important component of the openSUSE Tumbleweed process. I think because ttm only supports one job group (and no subgroups), currently "openSUSE Tumbleweed Kernel" is separate, next to "openSUSE Tumbleweed", the only job group that is looked at by ttm and hence the only job group that has direct impact if a build of openSUSE Tumbleweed will be released or not. To make the kernel tests take part in that decision ttm should be extended to support multiple job groups along with further changes to scale the whole development process based on multiple openQA job groups.


Related issues 1 (1 open0 closed)

Copied from openQA Project - action #40478: support multiple job groups for ttmNew2018-08-31

Actions
Actions #1

Updated by okurz over 5 years ago

  • Copied from action #40478: support multiple job groups for ttm added
Actions #2

Updated by jlausuch over 4 years ago

  • Parent task set to #58685
Actions #3

Updated by pvorel over 3 years ago

  • Parent task deleted (#58685)

Removing parent task.

Actions #4

Updated by pcervinka over 3 years ago

  • Tags set to openQA, openSUSE, tumbleweed, ttm, aged
  • Project changed from openQA Tests to 178
  • Subject changed from [kernel] proper integration of kernel tests into openSUSE Tumbleweed release process, e.g. teach ttm to support multiple job groups to Proper integration of kernel tests into openSUSE Tumbleweed release process, e.g. teach ttm to support multiple job groups
  • Category deleted (Infrastructure)
  • Target version set to 454
Actions #5

Updated by pcervinka over 3 years ago

  • Target version changed from 454 to 643
Actions #6

Updated by pcervinka about 1 year ago

  • Project changed from 178 to QA
  • Target version changed from 643 to future

There is nothing to do about this tool on our side.

Actions #7

Updated by okurz about 1 year ago

pcervinka wrote:

There is nothing to do about this tool on our side.

What do you mean by that? What changed in the past two years what wasn't mentioned here? If nothing changed then I assume the original motivation still holds. An alternative to changing ttm is of course to simply move more tests into the production job group

Actions

Also available in: Atom PDF