From fd90cf59dee7f310a41a415ab16126f6003d1d77 Mon Sep 17 00:00:00 2001 From: Khanh Tran <32532742+khanhtc1202@users.noreply.github.com> Date: Fri, 27 Dec 2024 10:13:42 +0700 Subject: [PATCH] Fix image link (#5459) Signed-off-by: khanhtc1202 --- docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md b/docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md index 088998a137..056460f965 100644 --- a/docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md +++ b/docs/content/en/blog/ci-cd-gap-fulfill-with-pipecd.md @@ -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.