-
Notifications
You must be signed in to change notification settings - Fork 25
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
fix: remove old workflows on addon checksum change #297
Conversation
d5f5b80
to
ba9998b
Compare
Codecov Report
@@ Coverage Diff @@
## master #297 +/- ##
==========================================
- Coverage 56.20% 55.81% -0.39%
==========================================
Files 14 14
Lines 1893 1933 +40
==========================================
+ Hits 1064 1079 +15
- Misses 715 734 +19
- Partials 114 120 +6
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
ba9998b
to
d81312e
Compare
Signed-off-by: Chun-Che Peng <chunche.peng@gmail.com>
d81312e
to
206d8c1
Compare
Signed-off-by: Chun-Che Peng <chunche.peng@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I think the Addon can still get stuck in pending if there's no further updates or controllers aren't updating... we can additionally add a check before return from addon-manager/controllers/addon_controller.go Line 350 in ef27eb5
|
Signed-off-by: Chun-Che Peng <chunche.peng@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fixes: #285 #174
with contribution from @estela-ramirez
a new addon (but has the same checksum from recent past) won't generate a new workflow since a previous workflow was already created; as a result, the addon gets stuck on pending
fix is to purge old workflows so a new workflow can get created