1 min read
When you connect your GitHub organization to Vercel, with Vercel for GitHub, we build and deploy your app for each every Git push. We call such an event a job.
For a given branch, we process each job in a queue. If multiple jobs are waiting, we pick the latest one to build. Vercel for GitHub will always give you the deployment URL for the most recent commit.
Link to headingIntroducing Auto Job Cancellation
As projects grow in size, builds tend to take longer. If you have regular commits coming in for these projects, one after another, the build time will add up and delay the deployment of the latest commit.
From today, Vercel will always build the latest commit immediately.
While waiting for build job to complete, if Vercel receives a new job from the most recent commit, we cancel the current job and start building the latest job.
With this new behavior, you can always get the deployment URL for the latest changes right away.
Link to headingOpt-out support
We think auto job cancelation is a tremendous new default behavior that will save you both time and money.
However, if you want every push to build in sequence, Vercel provides an option to be added in a vercel.json configuration file.
{
"github": {
"autoJobCancelation": false
}
}
Link to headingConclusion
Our goal for Vercel is always to provide deployments for any project as quickly as possible. We believe that this new Vercel for GitHub behavior that extends a great method to receive deployments from your most recent changes is a great benefit to this goal.
If you have any questions or feedback, we would love to hear from you. Feel free to always reach out to us.