A Git build can appear stuck when the build remains running, the build stream stops updating, or the deployment remains in building.
- Identifies common Git build failure points.
- Focuses on repository credentials, Dockerfile context, registry access, and build timeout.
- Helps you decide whether to retry, fix credentials, or adjust the build configuration.
- A Git deployment build does not finish.
- The build stream stops updating.
- A rebuild never patches the deployment image.
- A Git-backed deployment or build request.
- Access to build status or build stream.
- Repository and registry permissions.
Screenshot Required
- Open the deployment detail page.
- Check build status and build stream.
- Confirm repository credentials are valid.
- Confirm the branch, Dockerfile path, and build context.
- Check whether the image registry accepts pushes from Kubly.
- Retry the build after fixing credentials or build configuration.
- Retrying the same build without changing expired credentials.
- Using a Dockerfile path that exists locally but not in the selected branch.
- Ignoring registry push errors after the build step.
- Large builds may need more time depending on platform limits.
- Keep build logs available when asking an operator for help.