CODEWITHSUNDEEP
gitamazon-web-servicesgithubaws-amplify
CCCC
CCCC

Reputation: 6461

amplify - deployment not triggering after new merge

I've set-up a main branch in Amplify frontend.
Every time I have made changes on main branch, it should auto deploy a new version of frontend.

Everything works fine until today.
After I've merged dev branch to main branch in Github, I go to Amplify and find that the pineline is not running

It shows

Last commit: Merge pull request #230

But the latest one should be #232

How do I fix/debug it??

Upvotes: 1

Views: 2107

Answers (3)

amanpandey_11
amanpandey_11

Reputation: 1

I encountered same problem when, I changed my github credentials after a merge new changes in the production branch, but the deployment did not start when i opened amplify , after checking all the configurations that are properly configured. I got to know that some permission to amplify from my git were not granted Here are steps to resolver.

Reauthorize GitHub on aws Amplify

If the problem persist try looking out to your app and ensure automatic deployment is turned on

Upvotes: 0

Naveen Kumar
Naveen Kumar

Reputation: 424

In case there are others who don't know how to trigger a manual build with latest code... Today I found that it's possible to create a webhook and manually trigger a build. While this issue is being investigated, the webhook can be used as a workaround.

Amplify Console → Build settings → Incoming Webhooks → Create Webhook.

Then it's possible to use the curl command to trigger a new build.

Credit: https://github.com/aws-amplify/amplify-hosting/issues/400#issuecomment-582772160

Upvotes: -1

CCCC
CCCC

Reputation: 6461

I tried to re-connect repository as many developers suggest through the Internet, but it doesn't work for me.

Finally, I've created a webhook in Amplify so that I can trigger the deployment manually

Upvotes: 3

Related Questions