action #52679
open
[qe-core][qem][functional][network] Update Travis checker to limit usage of machines for the automatic tests to the automation infrastructure
Added by vpelcak almost 5 years ago.
Updated over 3 years ago.
Category:
Enhancement to existing tests
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.
- Category set to Enhancement to existing tests
- 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
- 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".
- Status changed from New to Workable
- 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
- 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
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 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