-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update timeout for GitHub workflows #5733
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5733 +/- ##
=====================================
Coverage 73.3% 73.4%
=====================================
Files 175 175
Lines 18147 18147
=====================================
+ Hits 13315 13325 +10
+ Misses 3856 3849 -7
+ Partials 976 973 -3 ☔ View full report in Codecov by Sentry. |
It seems that |
You can ask eng enablement team on |
d66f0e5
to
44fc6e6
Compare
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/8450669229 |
What this PR does / why we need it:
There are 29 PRs from @team-eng-enablement that set the default timeout for our GitHub workflows. This PR aims to do it in one shot.
Company wide
vars.GHA_DEFAULT_TIMEOUT = 10 minutes
for our use-case repo widevars.GHA_EXTENDED_TIMEOUT_MINUTES = 30 minutes
was defined tooSpecial notes for your reviewer:
I am wondering if I set it everywhere properly...