If your build fails with the command not found, then your dependencies have not been installed. To install your dependencies, upload a configuration file such as package.json for NodeJS programs listing all of the required dependencies.
If your build is failing with exit status 128, this likely means that we no longer have access to your GitHub repository. Ensure that your repo is public or that you gave us access by signing in through GitHub when providing the link to the repo.
Most likely, your assets are being loaded from incorrect URL like ipfs.io/app.js instead of ipfs.io/ipfs/$hash/app.js. If you want to support loading sites through IPFS Gateway, you need to make sure your assets are loaded from relative paths. Some frameworks supports homepage field in package.json:
This occurs when the number of builds across all of our customers exceeds our current network capacity. When this happens builds will be queued as they come in and be deployed when other builds finish
This occurs when the number of total builds across all of your sites exceeds the build limit. You can increase your concurrent builds by upgrading your account or by contacting support. If you have this issue, you can cancel other builds that may not be as important.