- In Settings > Auto Deploy, copy the Payload URL and Secret.
- Add a webhook to your repo, following the steps on screen (GitHub: content type
application/json, and choose Just the push event). - Push to the branch you set, then watch the build in the Builds tab.
Click New build to build yourself, Cancel build to stop, and Use this release to roll back. The latest 5 releases are kept. Build logs are kept for the 20 newest builds; older builds show that their log has expired.
If something goes wrong
I pushed but nothing was built
Look at the webhook delivery history in your repo settings: invalid webhook signature means enter the Secret again · branch … was not pushed means you pushed to a different branch · auto deploy is disabled means turn on Auto Deploy.
“คำสั่ง Build ล้มเหลว (exit code …)” (The build command failed (exit code …))
Open the log in the Builds tab to find the line that failed. Try running the same build command on your own computer with the same Node.js version.
“Build ใช้หน่วยความจำเกิน (exit 137)” (The build used too much memory (exit 137))
Do less work during the build, for example turn off source maps or split pages into smaller ones.
“Build ใช้เวลานานเกิน … ของแพ็กเกจ” (The build took longer than the plan’s … limit)
Maximum build time: Free 5 minutes · Starter 10 minutes · Business 15 minutes. Cut down the build steps or upgrade your plan.
“ไม่พบโฟลเดอร์ Output” (Output folder not found) or “โฟลเดอร์ Output ว่างเปล่า” (Output folder is empty)
Set the output folder to match what your framework creates (such as dist, out or build). Next.js needs output: 'export'.
“Access token ไม่ถูกต้องหรือหมดอายุ” (The access token is invalid or has expired) or “ไม่พบ repository” (Repository not found)
Create a new token following the table above, and check the branch name. A private repo always needs a token.
“โควตา Build หมดแล้ว” (Build quota used up)
Wait for the new day’s or new month’s quota, or upgrade your plan. Builds that fail because of a problem on our side are given back to your quota.