Project

General

Profile

action #52679

[qe-core][qem][functional][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure

Added by vpelcak about 2 years ago. Updated 8 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Enhancement to existing tests
Target version:
Start date:
2019-06-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

We should not use IPs and hostnames of machines that are not part of the automation infrastructure on site.

We need to find the right balance between real world scenarios and prevention of unnecessary failures.

History

#1 Updated by SLindoMansilla about 2 years ago

  • Category set to Enhancement to existing tests

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

#2 Updated by SLindoMansilla about 2 years ago

  • Subject changed from Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure to [tools] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure

#3 Updated by okurz over 1 year ago

  • Subject changed from [tools] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure to [qam][functional][u][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure
  • Priority changed from Normal to Low
  • Target version set to future

SLindoMansilla as I understand this concerns os-autoinst-distri-opensuse only so it's rather an issue to be solved by the teams involved in the network related test modules of os-autoinst-distri-opensuse, not "tools".

#4 Updated by tjyrinki_suse about 1 year ago

  • Status changed from New to Workable

#5 Updated by tjyrinki_suse 9 months ago

  • Subject changed from [qam][functional][u][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure to [qe-core][qam][functional][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure

#6 Updated by tjyrinki_suse 8 months ago

  • Subject changed from [qe-core][qam][functional][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure to [qe-core][qem][functional][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure

#7 Updated by riafarov 8 months ago

I strongly disagree with the priorities, as now CI might take up to 10-12 hours, which forces us to multitask and slow down the progress with the changes, so I would raise the priority here, so we can clarify budget related questions and then solve technical part.

#8 Updated by okurz 8 months ago

riafarov wrote:

I strongly disagree with the priorities, as now CI might take up to 10-12 hours, which forces us to multitask and slow down the progress with the changes, so I would raise the priority here, so we can clarify budget related questions and then solve technical part.

riafarov this ticket is not about travis CI in general but rather a specific "check in CI".
The general "travis CI takes 12 hours" task would be my newly created #80394

Also available in: Atom PDF