Why does Vercel "skip" commits and doesn't trigger a deploy? Project running behind (latest git commits not recognized)

[kyr0]

Hi,

I've a project setup with a public GitHub repo: https://github.com/kyr0/turbo-hybrid-astro-on-vercel
The Vercel project is configured to deploy from the main branch.

When I push, Vercel triggers deploys, but only occasionally. It often "hangs" behind and doesn't recognize the most recent comments.
For every commit, where it worked as expected, you can see a comment attached to the commit:

The Vercel App in GitHub is configured correctly and I already re-connected the integration to double-check. I also changed the branch name forth and back to main to double-check and started some Deploys manually, but when I do, Vercel still deploys from the old commit, not from the most recent one.

Nothing helps, the last commit Vercel currently "sees" remains f77c10a at the time of writing this (4 commits behind).

This behaviour doesn't make sense to me. It looks like a background sync process is too slow or some cache invalidation doesn't work well.

I can manually deploy as often as I want - deploys works, but it always picks the same old commit from the main branch until it finally finds the latest one after many minutes or even hours. And yes, of course I pushed to the remote; the difference between what Vercel sees as latest commit and what is on Github (main) can be verified by checking the repo commit history on Github and comparing with the screenshots below:

Here is the views from the Vercel UI:

It really doesn't want to pick the latest commits.

Do you have any ideas?

Thanks and best!

[amyegan]

Hi @kyr0! My first thought is you may have configured Ignored Build Step at some point, maybe with something like turbo-ignore which could interfere with builds.

[kyr0]

@amyegan Thank you, Exactly! Unfortunately, I didn't see your answer and tried a few more times to debug the issue.
So I had to find it out the hard way xD Yes, indeed, turbo-ignore seems to be buggy or my turbo configuration is flawed (but it looks correct to my eyes tho).

One thing I didn't notice before was this beautiful drop-down hiding the cancelled deployments:

Now with that one enabled, it's reveals, what happened (after clicking inspect deployment):

For now I disabled the ignore build step by configuration:

{
  "framework": "astro",
  "devCommand": "cd ../.. && yarn dev",
  "buildCommand": "cd ../.. && yarn build",
  "installCommand": "yarn --cwd=../.. install --frozen-lockfile",
  "ignoreCommand": "exit 1",
  "cleanUrls": true
}

[amyegan]

I'm glad builds are working for you now! I'll share this feedback with the team ❤️

[AlejandroSanchez90]

hi im triying to fix my deployment getting skipped aswell, where should i put that information, its my first time working with vercel, i started it as a create-next-app and dont have a vercel config file, how should i init it?

[Aliniroomand]

@amyegan I hope you best wishes by my heart...
I've been struggling and searching about 2 days for solving this problem and nothing found but the only way that really worked was turbo-ignore...
thank you so much....

[tknickman]

@kyr0 glad you got things building! I wanted to add a little more info about turbo-ignore so hopefully you can still make use of it in the future. The way that turbo-ignore works is by finding the app at the root of your vercel project (for your project in this case, this is apps/server).

Then, for each build on Vercel, it checks to see if server itself, or any of servers dependencies within the workspace (which in this case, is only eslint-config-custom, tsconfig, and format) have changed between the current commit, and the last successfully deployed commit for your current branch.

If nothing is found - the build is ignored because turbo-ignore believe that the changes are not relevant to the app.

For example, any changes in README.md, public/ or apps/static would not trigger a build. However changes in apps/server, or packages/format would.

Hopefully that's helpful!

As an aside, we're working to make the docs here better so this is less "magic" and more understandable moving forward!

[perov93]

Quick solution, if someone is having problem with latest commit:

https://vercel.com/changelog/manually-create-deployments-by-commit-or-branch-in-the-dashboard

Hope it will help someone :)

[tella-john]

This works great, thanks! The underlying link is pointing to a different page though - here's a working link:
https://vercel.com/changelog/manually-create-deployments-by-commit-or-branch-in-the-dashboard