Closed chkrause closed 3 years ago
We are facing the exact same issue. Auto deploy was working fine for months until a few days ago. It appears it may be an issue with Amplify's subscription to the SNS topic. I've added a second subscription to the topic that sends me an email and I can see that CodeCommit is indeed dropping a message on the SNS topic because I receive an email when I push a commit, but Amplify doesn't run the auto build/deploy. I've also added a webhook to manually deploy and this works fine. The behavior I see is that if I run a manual deploy via the webhook, then the very next auto deploy will run successfully. I see the same odd layout changes in the UI mentioned by @chkrause where it shows the green "deployment successfully completed" progress bar rather than the provision/build/test/deploy/verify steps. After that successful build, subsequent code commit changes will not trigger an auto deploy. We get the same behavior if we disconnect the branch and then re-connect it. The first commit will trigger an auto deploy but subsequent ones do not. We have all the exact symptoms described by @chkrause such as empty build history, no deployment logs, etc.
Resolving due to age - please re-open if you are still experiencing issues.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Since 28th of January we facing issues with the configured CD via Code-Commit.
After committing a change the amplify deployment isn't triggered any longer.
Steps to reproduce:
Connect Branch via Code-Commit (Mono-Repository) => Deployment runs sucessfull
Commit change to code-commit => Deployment is triggered, layout has changed, but deyployment seems be be fine a. Trigger Event from CodeCommit to SNS Topic “amplify_codecommit_topic
Any additional change to code-commit will not trigger new deployments a. Trigger Event from CodeCommit to SNS Topic “amplify_codecommit_topic
b. Build-History is broken and dosn't display anything c. Deployment Logs only avilable by manipulation of URL