Builds Not Completing

Problem

My Probo.CI build is not completing. It seems to hang during the build process on a single step, sometimes the final step and does not complete. This will also cause the Visit Site link to not become available. The status beside the build step is yellow.

Solution

This can be caused by two main reasons. This can be a common occurance on NodeJSApp builds when you are not using pm2 in your buildCommand. Many Node.js builds will stay in the foreground and not release back to the terminal - especially when compiled in a watch or development build mode. See the Node.js documentation page for complete details on this under the buildCommand section.

It can also be caused by certain errors in the build process. These are typically caught at build time, but due to the nature of how Probo.CI builds applications it is possible the build could crash withouth reporting it. we’re working to do a better job reporting these errors, but because they occur inside the application container itself and not an actual crash of Probo.CI, it is difficult to pinpoint errors for the purposes of reporting. The best bet is to review the build step and see if you can see where any errors are being reported.

Some builds may appear to be stuck but in reality they are just working through complicated tests or imports. This is common around large database imports, search indexing or automated tests. If the logs stop streaming on a particular build it does not mean the build has stopped, it may just be working behind the scenes. We’re constantly working to improve our build output display to give you the most up-to-date information about your build and its process.

Due to the nature of Probo.CI, it is possible that builds may appear to timeout and never complete. It happens. This can happen if a process times out on the display or the telemetry on a build stops for any reason. THe best thing you can do in this instance is use the rebuild icon on that build to try the build again, and delete the old build. Keep in mind if a build does not finish, it will still register in your queue. Be sure to check to make sure you do not have a stuck build (in progress) clogging up your queue by deleting them.

The best advice we can give to reduce build times is to keep your database imports as lean as possible and limit the number of steps in your build as best you can. Don’t short-change yourselve, but understand a build with 50 tests could take hours to complete depending on the nature of the testing - and in that time, processes in and out of the application can timeout.

Related Articles & Information

---

Rebuilding Without a Pull Request Builds Don't Trigger