Diff check before auto deploys for monorepo

[cyrus-za]

Following the launch of monorepo support and the hotly discussed topics at #3547 I figured it makes sense to start splitting up some of the points discussed there into their own issues, starting with this feature request: do a diff check on the git integration to see which directories changed and only deploy the services that are affected for these directories.

e.g.
If I have a monorepo with lets say 2x nextjs apps and 1x backend node server, and I push a commit to a branch that has changes to app1 and server1 but does not affect app2, I'd expect only app1 and server1 to be affected.

[paulogdm]

Check if https://vercel.com/docs/platform/projects#ignored-build-step can't assist you temporarily.

[josias-r]

@paulogdm It seems to me grep is not working. The following two examples always cancel:
echo master | grep -q master && exit 1 || exit 0
echo develop | grep -q master && exit 1 || exit 0
even though only the second one should, correct?

[josias-r]

Nor does something work like [[ "master" == "master" ]] && exit 1 || exit 0. It will throw an error.
Error: Command failed with ENOENT: [[ "master" == "master" ]] && exit 1 || exit 0

When rolling out a feature like that, give some info on what the devs can work with :)

[paulogdm]

We've just released a guide about this field: https://vercel.com/knowledge/how-do-i-use-the-ignored-build-step-field-on-vercel

[josias-r]

@paulogdm Awesome, thanks!

[osdiab]

@paulogdm i've tried literally copy and pasting the exact scripts in that article but they never seem to actually work; it would be really helpful if I could see logs from these ignore build step tasks. No idea what's going wrong but the environment variables don't seem to be getting filled in despite clicking the "automatically expose system environment variables" checkbox in the console and running bash scripts that exactly match the examples in the article above.

[cyrus-za]

Thanks for this. Is this new? I did not see it when I checked for it a week ago?

I went through it, setup a bash script, but it's not working, despite giving the correct exit code when testing locally and I cant see any logs on the vercel build step. Any help would be appreciated

[paulogdm]

It is! The feature is live since we released support for monorepo.

[cyrus-za]

@paulogdm I think I figured out why the script is not working. Do you clone with a depth=1 and only the current branch? So no way to compare with master?

[ironhee]

@paulogdm I now have a new problem. We are running into a rate limit. It appears that each cancelled build for each of our projects in the monorepo count towards the rate limit. Can you please fix this?

I'm also having a rate limit problem. Do you have any solution to this issue? @paulogdm

[ironhee]

The Ignored Build Step works fine. The only problem is that ignored deployments are included in the rate limit.

[paulogdm]

We have an internal task to remove the rate-limit for canceled builds.

[cyrus-za]

@paulogdm can we also get it to not show cancelled builts in the list, or on github integrations? Its a little annoying to see all our apps when only a single app was affected

[paulogdm]

Absolutely @cyrus-za . The current way is just sub-optimal DX-wise. Please talk with your CSM (Evelynn) about this so we can make sure this feature gets released.