-
Notifications
You must be signed in to change notification settings - Fork 183
Add a blog: What Happens before Deployment #5788
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
Conversation
Signed-off-by: t-kikuc <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5788 +/- ##
========================================
Coverage 27.17% 27.18%
========================================
Files 507 507
Lines 53423 53533 +110
========================================
+ Hits 14520 14553 +33
- Misses 37796 37866 +70
- Partials 1107 1114 +7 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2. Determine stages | ||
|
||
The planner instance runs as a goroutine in a 1:1 relationship with Deployment, allowing multiple deployments to be processed concurrently. | ||
Also, control is implemented to prevent multiple deployments from running simultaneously for the same application. |
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.
Also, control is implemented to prevent multiple deployments from running simultaneously for the same application. | |
Also, piped is implemented to prevent multiple deployments from running simultaneously for the same application. |
nits
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.
Thank you!
I fixed it : 99b1071
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.
Great article, can't wait to see it online 💯
Signed-off-by: t-kikuc <[email protected]>
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, thank you!
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.
Looks Great!
I commented on one nitpick.
Deployment is triggered when an application meets all four of the following conditions: | ||
|
||
1. "Automatic deployment on drift detection" is enabled | ||
- Set the `trigger.onOutOfSync.disabled` item to `true` (**default is `false`**) |
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.
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.
Thank you, I fixed it: 91d3f79.
I confused the double negative of disabled
😅
This trigger is disabled by default,
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.
@khanhtc1202 Sorry, please re-approve 🙏
Signed-off-by: t-kikuc <[email protected]>
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 👍🏻
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.
👍
What this PR does:
as title
translated from my Japanese article: https://zenn.dev/cadp/articles/pipecd-before-deployment
Why we need it:
It helps to understand the core mechanism for PipeCD users and contributors.
Which issue(s) this PR fixes:
Does this PR introduce a user-facing change?: