-
Notifications
You must be signed in to change notification settings - Fork 150
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
github: reuse existing deployment when sending new notification #235
github: reuse existing deployment when sending new notification #235
Conversation
538dbb2
to
bbbd023
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #235 +/- ##
==========================================
- Coverage 55.05% 54.79% -0.27%
==========================================
Files 35 35
Lines 3360 3376 +16
==========================================
Hits 1850 1850
- Misses 1238 1254 +16
Partials 272 272 ☔ View full report in Codecov by Sentry. |
Hi @jaredtbates I saw that you mentioned in your Initial pull request that you didn't find a way to preserve deployment id, what do you think about this patch? |
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.
This looks awesome to me! This is a smart solution.
bbbd023
to
83df819
Compare
@MrFreezeex could you please resolve conflicts and make sure that you have added tests? |
Try to list existing deployment with the same sha/environment/ref and reuse it if found. This allows ArgoCD notification to update the same deployment with multiple deployment status instead of creating a new one on each deployment notification. Signed-off-by: Arthur Outhenin-Chalandre <[email protected]>
83df819
to
f523570
Compare
Hi @pasha-codefresh! I just rebased the code but I can't realistically add test unfortunately. This whole function is not tested and AFAIK there are no tests on any |
LGTM, thank you |
Try to list existing deployment with the same sha/environment/ref and reuse it if found. This allows ArgoCD notification to update the same deployment with multiple deployment status instead of creating a new one on each deployment notification.