Closed sachsom95 closed 1 year ago
I can debug this myself if someone can point me to logs on the actual triggers
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
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.
Before opening, please confirm:
App Id
d3dvg63bsgcr6q
AWS Region
eu-west-1
Amplify Hosting feature
Frontend builds
Describe the bug
We have a production amplify setup with GitLab CI/CD. The GitLab CI/CD is connected via branches. Whenever a merge is made on any of the releases branches a build is initiated and deploys to the appropriate domain. Today at 17:30 GMT we had a merge that was pushed to the branch initiating a build that was successfully built and deployed. 2 hours later we start getting notified that a new deployment has started. This keeps happening continuously every 20-odd minutes.
I've tried going to the branches section and disabling auto-build on the branch and it still continues to build. I am attaching the build history and branch screenshots here
Expected behavior
Reproduction steps
This step is not available as it seems to be specific to just us
Build Settings
Log output
Additional information
The issue is with the branch release/dev