Skip to content
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.

Sign up for GitHub

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 image link #5459

Merged
merged 1 commit into from
Dec 27, 2024
+1 −1
Merged

Fix image link #5459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ Each event sent to PipeCD to trigger a deployment can actually be shared to trig

This becomes problematic when a development team includes many people working on the same repository and the number of changes affecting many services is large enough: PipeCD's current UI deployment list makes it difficult to determine exactly which deployments were triggered by which code change.

![](/images/problematic-deployment-list-ui.png)
![](/images/problematic-deployment-list-ui.jpg)

Naively, we could just add a `root_cause_commit_hash` or `codebase_commit_hash` field to PipeCD’s deployment model and use this information to filter deployments triggered by the same repository code change in the PipeCD UI.

Expand Down
Loading