Dojo
Dojo is BuildNinja’s interactive sandbox environment where you can experiment with build configurations, simulate builds, and understand how execution works without impacting real projects.
Dojo runs independently from your production environment and requires no setup.
How Dojo Works
Dojo is a shared sandbox designed for learning and experimentation. This environment provides a fully functional BuildNinja experience while applying usage limits to ensure fair access and system stability for all users.
Sandbox Limitations
Dojo is a temporary sandbox environment with the following constraints:
- The sandbox resets automatically every 6 hours
- All user-created projects, build history, and artifacts are removed during reset
- Each build has a maximum execution time of 5 minutes
- The environment is shared with other users
These limitations help keep Dojo fast, reliable, and safe to use.
Template Projects
Dojo includes a set of preconfigured template projects to help you get started quickly.
- Template projects are automatically pinned in the Projects view
- They demonstrate common BuildNinja use cases and features
- Template projects cannot be unpinned or removed
- You can create and manage your own projects alongside them
Authentication and Access
You can access Dojo using the same email address and password you used to register on the BuildNinja website. Authentication is handled automatically, and no additional setup is required.
Data Persistence
Dojo does not retain data permanently. If you want to keep build configurations, logs, or outputs, copy them externally before the next sandbox reset.
What You Can Do in Dojo
- Create and edit build configurations
- Run simulated builds in a safe environment
- View execution logs in real time
- Test failure scenarios without risk
- Understand step-by-step build execution behavior
Suggested Exercises
| Exercise | What You Do | What to Observe |
|---|---|---|
| Run Your First Build | Open Dojo and run the default build configuration | How each step executes and completes |
| Break the Build | Modify a build step (for example, use an invalid command) and rerun the build | How failures are detected and reported |
| Add a New Step | Add a custom step to the build and rerun it | Execution order and step behavior in logs |
| Simulate a Real Workflow | Create a multi-step build (install, test, and build) | End-to-end execution output and logs |
Best Practices
- Start with simple builds before adding complexity
- Test one change at a time
- Use logs to understand failures
- Recreate real-world scenarios before applying changes in production
Enter the Dojo
Practice BuildNinja builds in a safe, interactive environment.
Launch DojoNo installation required • Full features • Resets every 6 hours