-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify Preview Status not update in Github Action #3287
Comments
Hi @jackykwandesign 👋🏽, thanks for raising this issue. We are working on reproducing this behavior and adding it to our product backlog for prioritization. |
Hi @jackykwandesign 👋 , thanks for raising this and apologies for the delayed response on this thread. I was unable to reproduce the outlined behavior when implementing the following workflow:
Are you still experiencing this issue? If yes, can you please share your workflow with detailed steps so we can reproduce it on our end. |
We are experiencing this issue as well Info
Our Setup
So, in this case maybe the issue is that the Amplify build didn't terminate when it detected nothing else needs to be done |
@jackykwandesign @alexilyaev We pushed a fix for this issue last week - |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
Before opening, please confirm:
App Id
d9yldpv6pkjrw
AWS Region
ap-southeast-1
Amplify Hosting feature
Web previews
Describe the bug
same as #1458 (comment)
When multiple PR trigger build in Amplify, it will never update Github CICD status check,
stuck at building forever
But in AWS amplify console, it show finish status
Expected behavior
Github CICD status always show correct status, or we can trigger job rerun in github action
Reproduction steps
Trigger amplify preview with two branch running at the same time, so if job B start running when job A not finish yet, they will stuck forever
Build Settings
NA
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: