[ECS] PipeCD failed to recognize last success deployment in PlanPreview
Open
@gitcommitankit is already working on this.
Since Jun 23, 2025.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
- During the first deployment of a service, that deployment failed so the next PR for fixing that service will always lead to the below error
Error:Reason: failed while calculating diff, cannot get the old manifests without the last successful deployment
What you expected to happen:
- If the first deployment of a service failed, the next Plan Preview for that service should consider it as a new deployment instead of finding last successful deployment.
How to reproduce it:
- Create PipeCD
app.pipecd.yamlconfig file. - Create an app on the Web UI.
- Let that first deployment fail.
- Create another PR to fix that first deployment.
Environment:
pipedversion:v0.51.0control-planeversion:v0.51.0- Others:
actions-plan-preview: v1.7.6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.