What a failed deploy costs
A failed deploy is quiet. The site is still up, so nothing looks wrong. The feature you announced is not there, the bug you fixed is still there, and every later change is stuck behind the broken one.
For a solo builder it is worse: if you do not read build logs, you may not know why it failed, or that it failed at all.
What Bugstack does
Bugstack does autonomous software maintenance. For deploys:
- It hears about the failure. Render tells Bugstack when a deploy fails, once you have connected it.
- It reads the build log and the commits between the last good deploy and the failed one.
- It names the cause. The pull request says which change broke the deploy, and quotes the line from the log that shows it.
- It opens a pull request with one of two things: a fix, or a change that restores the last commit that deployed.
- It says what it could not check. If it could not run your build, the pull request says so.
If the failure looks like a one-off, such as a network blip during install, Bugstack on Autopilot retries the deploy once for that commit and then asks you.
An example
From a real Bugstack pull request on our own repository:
- What happened: the dashboard build failed at the compile step.
- Why it broke: a commit made one package import server-only modules at the top of a file that the web bundle also loads.
- What it changes: the package loads those modules only when it needs them.
- Risk: it named the one situation where the change would silently do nothing, and said it had not run the build.
What it does not fix
- Causes outside your code. A missing environment variable or a setting on your host is reported, and no code change is opened.
- Other hosts. Deploys on hosts other than Render are not seen today.
How to start
- Sign in with GitHub and start the 14-day trial. It includes $50 of credit.
- Install the Bugstack GitHub App on your repository.
- Connect Render in Settings, under Connections. It takes a webhook address and a signing secret, and a Render API key so Bugstack can read the build log.
No SDK is needed for deploy fixes.
Questions
Which hosts does Bugstack support for failed deploys?
Render. Other hosts are not supported for this job yet.
Will it roll back my site on its own?
By default, no. It opens a pull request that restores the last good commit, and you merge it. Rolling back on its own is a setting you can turn on for a repository on Autopilot.
Does it need access to my Render account?
It needs the webhook, which tells it a deploy failed, and a Render API key to read the deploy’s log and settings. It reads the names of environment variables and never their values.