🔺Resolving failed migration on Vercel Preview
Last updated
Was this helpful?
.svg?alt=media&token=8debffef-3fb7-4216-a33f-989bd30e23d3)
Last updated
Was this helpful?
We currently use a single DB for all preview deployments corresponding to various branches. (There is on going work to have different DB per branch. This approach would still remain applicable as repeat deployments of same branch would fail.)
Sometimes, a faulty migration in one of those in progress branches, can fail which can start failing all builds of other branches as well.
Get the name of the failed migration(e.g. in the above case it is 20220714175322_destination_calendar_one_to_many_bookings)
Go to prisma folder in the repo. Modify DATABASE_URL temporarily to Preview DB. You can get the credentials from Vercel Environment Variables(Preview). It might be a good idea to have that variable remain there as commented, so that you can easily switch
Once, you have ensured that, DATABASE_URL is updated, run following command from prisma folder yarn prisma migrate resolve --rolled-back 20220714175322_destination_calendar_one_to_many_bookings. This should fix the rollback the failed migration ensuring all other branches deploy fine.
Note that the branch having the issue should fix the migration problem to avoid this issue from coming again and again.
