Skip to content

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

Merged
merged 3 commits into from
Apr 30, 2025
Merged

Conversation

t-kikuc
Copy link
Member

@t-kikuc t-kikuc commented Apr 28, 2025

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?:

  • How are users affected by this change:
  • Is this breaking change:
  • How to migrate (if breaking change):

@t-kikuc t-kikuc enabled auto-merge (squash) April 28, 2025 12:57
Copy link

codecov bot commented Apr 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 27.18%. Comparing base (b9293a3) to head (91d3f79).
Report is 5 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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

Copy link
Member Author

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

Copy link
Member

@khanhtc1202 khanhtc1202 left a 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 💯

khanhtc1202
khanhtc1202 previously approved these changes Apr 30, 2025
Copy link
Member

@khanhtc1202 khanhtc1202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

Copy link
Member

@Warashi Warashi left a 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`**)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default is true and set false to enable this option.
スクリーンショット 2025-04-30 13 30 08

Suggested change
- Set the `trigger.onOutOfSync.disabled` item to `true` (**default is `false`**)
- Set the `trigger.onOutOfSync.disabled` item to `false` (**default is `true`**)

Copy link
Member Author

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,

Copy link
Member Author

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 🙏

Copy link
Member

@Warashi Warashi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏻

Copy link
Member

@khanhtc1202 khanhtc1202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@t-kikuc t-kikuc merged commit dfa7d78 into master Apr 30, 2025
19 checks passed
@t-kikuc t-kikuc deleted the blog-gitops-mechanism branch April 30, 2025 07:45
@github-actions github-actions bot mentioned this pull request May 15, 2025
@github-actions github-actions bot mentioned this pull request May 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants