Project

General

Profile

Actions
Copy link

action #134810

closed

[tools] GitlabCI deploy on salt-states-openqa took too much time

Added by osukup 8 months ago. Updated 8 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
livdywan
Category:
Regressions/Crashes
Target version:
Ready
Start date:
2023-08-30
Due date:
% Done:

0%

Estimated time:
Tags:
gitlab, infra

Description

https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/1790871

gitlab CI limit for single job is 2 hours, job took more..

Related issues 1 (0 open — 1 closed)

Related to QA - action #133457: salt-states-openqa gitlab CI pipeline aborted with error after 2h of execution size:MResolvedokurz

Actions
Actions
Copy link
 #1

Updated by okurz 8 months ago

  • Related to action #133457: salt-states-openqa gitlab CI pipeline aborted with error after 2h of execution size:M added
Actions
Copy link
 #2

Updated by livdywan 8 months ago

  • Status changed from New to Blocked
  • Assignee set to livdywan

I will probably look into that since it's basically a follow-up to my existing ticket. Seems the improvements were not enough just when I thought we hadn't seen any issues for a while.

Actions
Copy link
 #3

Updated by osukup 8 months ago

plus we have much more machines in salt now --> it probably needs split deploy to more independent groups ?

Actions
Copy link
 #4

Updated by okurz 8 months ago

  • Category set to Regressions/Crashes
  • Status changed from Blocked to Rejected
  • Target version set to Ready

closing as rejected.

osukup wrote in #note-3:

plus we have much more machines in salt now --> it probably needs split deploy to more independent groups ?

Yes, but salt triggers the execution on machines in parallel so this would only help if we can clearly identify which are the slowest and will stay the slowest every time.

Actions
Copy link

Also available in: Atom PDF