Actions
action #134810
closed[tools] GitlabCI deploy on salt-states-openqa took too much time
Start date:
2023-08-30
Due date:
% Done:
0%
Estimated time:
Description
https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/1790871
gitlab CI limit for single job is 2 hours, job took more..
Updated by okurz about 1 year ago
- Related to action #133457: salt-states-openqa gitlab CI pipeline aborted with error after 2h of execution size:M added
Updated by livdywan about 1 year 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.
Updated by osukup about 1 year ago
plus we have much more machines in salt now --> it probably needs split deploy to more independent groups ?
Updated by okurz about 1 year 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