Follow a build and troubleshoot
A slice that has been built carries its build: what the builder is doing now, every attempt it made, what it says about the specifications, and the gaps it filled. Use it to review what was built, and to find out why a slice is not moving.
Follow a build
Section titled “Follow a build”Open the slice’s build with Open the build of this slice. You see:
- Progress: the step the builder is on now and its Log. Anything that looks like a credential is removed before a log line is kept.
- Attempts: for each attempt, the Part (Backend, User interface or Removal), the Builder, the Outcome, the Time and the Tokens used.
- Specifications: what the builder says about each specification (Builder says) beside the board’s own run (Board’s run), and where they disagree.
- Assumptions: gaps the builder filled. Accept one that is right, or Dismiss it once the model says it.
An attempt ends as Built, Nothing to build, Blocked, Failed, Builder stopped answering, Ran out of time or Cancelled.
You can cancel a build that is running. The builder loses its lease, and the slice goes back to the status it had.
Rebuild a slice
Section titled “Rebuild a slice”A slice is built again when it becomes Ready for implementation again. What happens when a built slice changes depends on the application’s When a built slice changes setting: it is either marked out of date until someone makes it ready for implementation, or rebuilt automatically. See Choose who builds.
Stop using a builder
Section titled “Stop using a builder”A maintainer removes a builder under Organization settings > Builders with Remove. Its next request is refused. A slice it holds is offered again once its lease runs out. Choose another builder for the applications that used it.
Troubleshooting
Section titled “Troubleshooting”| You see | What it means |
|---|---|
| No code is shown after running the command | The builder could not reach the address. Builders only dial out, so check that the machine can reach Studio over HTTPS |
| Registration expired | The code was not approved within 15 minutes. Run the command again for a new one |
| Declined | A maintainer declined it. Register again to ask once more |
| The list says only maintainers can see builders | You are not a maintainer. Connect the builder, then ask one to approve it |
| A slice stays Ready for implementation | Its builder is offline, or busy with other work, or the slice waits for slices it builds on. It is taken as soon as the builder asks for work |
| A slice is Blocked | The builder said it could not continue, or failed on its last attempt. The reason and questions are on the slice. After three failed attempts, the loop stops retrying |
| Builder stopped answering | The builder did not renew its lease, so the attempt counted as failed |
| This builder speaks an older protocol. Upgrade it. | The builder needs upgrading before it can take work |
cratis build run stops because the project has uncommitted changes |
The CLI commits only a build’s own work. Commit or stash your changes, then start it again |
| An attempt failed with The generator … exited with a number | The --exec command failed. Run it on the same order with cratis build once to see why |
| An attempt failed with Verification failed | A --verify command, or one of the kit’s, exited with an error after the build. The end of its output is in the error |
| A builder run by the Cratis CLI shows no Progress | The CLI does not send progress reports. Follow the build in its terminal or service log |
| A builder is never offered the user interface of a slice | It does not build user interfaces. A Cratis CLI builder builds them only with a build kit that has ui |
Related
Section titled “Related”- The build loop explains offering, leases, retries and how a slice is settled.
- Build and deliver shows the build from the board’s side.
- Build a builder, when no existing builder fits your stack: the Cratis CLI with a generator of your own.