Skip to content

Commit

Permalink
Fix image link (#5459)
Browse files Browse the repository at this point in the history
Signed-off-by: khanhtc1202 <[email protected]>
  • Loading branch information
khanhtc1202 authored Dec 27, 2024
1 parent 18aa76f commit fd90cf5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md
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

0 comments on commit fd90cf5

Please sign in to comment.