-
Notifications
You must be signed in to change notification settings - Fork 593
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(ci): fix e2e's artifact name #6768
Conversation
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/12157169845 |
f643ea0
to
2f58cf8
Compare
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/12157490093 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6768 +/- ##
=======================================
- Coverage 79.9% 77.7% -2.3%
=======================================
Files 207 207
Lines 24588 24599 +11
=======================================
- Hits 19665 19120 -545
- Misses 3925 4500 +575
+ Partials 998 979 -19 ☔ View full report in Codecov by Sentry. |
2f58cf8
to
cf199b6
Compare
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/12157983914 |
cf199b6
to
6dd7bdb
Compare
The artifact issue has been resolved.
|
What this PR does / why we need it:
Fix the issue that occurred in https://github.com/Kong/kubernetes-ingress-controller/actions/runs/12156398089/job/33900270172#step:13:19.
The culprit is that when workflow fails,
KONG_IMAGE_ARTIFACT
is not set so there's a duplicated artifact name across tests against released and unreleased Kong.