Build automation and scheduling
Start builds from Git activity or on a schedule. Use branch, commit, and author filters to focus triggers on the changes that matter to your workflow.
Watch build automation demoFeatures
BuildNinja brings the everyday work of CI/CD together: configure the pipeline, run it on your infrastructure, follow the result, and understand what needs attention.
Connect your repository, configure the steps, and keep the outputs your project needs.
Set Up Your First ProjectStart builds from Git activity or on a schedule. Use branch, commit, and author filters to focus triggers on the changes that matter to your workflow.
Watch build automation demoConnect GitHub, GitLab, or Bitbucket. Keep repository changes and build activity close together, so the team can see what went into a run.
Watch Git integration demo01 Command Line & Script Runner02 Config File & AI Runner03 MSBuild, VSTest, SSHCommand Line · Script · Config · MSBuild · VSTest · SSH · AI
Execute build workflows with 7 dedicated runners: Command Line Runner, Script Runner, Config File Runner, MSBuild Runner, VSTest Runner, SSH Runner, and AI Runner. Configure parameters to make steps modular and reusable.
Watch pipeline runners demoKeep the outputs your build produces and use your configured deployment steps to move the right files to the next environment.
Watch artifacts and deployment demoSend useful build updates through your configured email service, with enough context for the team to respond.
View Notification Settingsstorefront-api · main
Send build updates through your configured email service. Use notification settings and mail templates to give the right people useful context.
Watch notifications demoChoose compatible build environments and bring your team into the workflow.
Read Install GuideRun builds on Windows, Linux, and macOS agents. Match work to compatible environments and see which agents are available or busy.
Watch agent management demoOrganize project membership and permissions so people have the access their work requires.
Watch access management demoConnect supported identity providers—Microsoft Entra ID, GitHub, GitLab, Google, and Bitbucket—to fit sign-in into the way your team manages access.
Watch SSO demoChoose the installation path that suits your environment. Follow the setup guides to configure the server, database, and agents.
Watch installation demoUse the dashboard to follow results and activity. Inspect the runs that need attention and check the capacity available to handle upcoming work.
Understand a failed build, explore a configuration, and review code-change insights in the workflow you already use.
The build log and changed file stay connected as AI explains what needs attention.
Illustrated product workflow01dotnet build Docs.Site.csproj
02error CS0246: PageModel could not be found
03Build failed. Exit code: 1
− // using Microsoft.AspNetCore.Mvc.RazorPages;+ using Microsoft.AspNetCore.Mvc.RazorPages;12:25:04 Checkout repository completed
12:25:05 dotnet build Docs.Site.csproj
12:25:06 error CS0246: The type or namespace name
'PageModel' could not be found.
12:25:06 Build failed. Exit code: 1
The changed file references PageModel without importing its namespace. Review the using directives and project references.
Review the reported error, inspect its context, and continue the investigation in AI chat.
Create credentials, choose a quality setting, set application limits, and follow usage in the kenzoAI portal.
Bring project members and permissions into the same management workflow.
Inspect repository activity alongside the work it triggers, so the team can connect a build with its source changes.
src/Program.csWhen a build fails, inspect the execution log and follow the output from the relevant step. Use the log itself and build intelligence to guide your investigation.
Execution-log caption: Example build output. Actual messages depend on your tools and build steps.
Windows · Linux · macOS
Commands · Scripts · SSH
MSBuild · VSTest
Docker · Kubernetes workflows
Google · Microsoft Entra ID
| Workflow | Supported tools or approach |
|---|---|
| Repositories | GitHub, GitLab, Bitbucket, Git |
| Identity | Microsoft Entra ID, GitHub, GitLab, Google, Bitbucket |
| Build machines | Windows, Linux, macOS |
| Containers and deployment steps | Docker and Kubernetes workflows using your configured tools |
| Execution | Command Line Runner, Script Runner, Config File Runner, SSH Runner, AI Runner |
| .NET build and test steps | MSBuild Runner, VSTest Runner |
| Reusable configuration | Parameters and supported YAML export and reuse |
Start with the interactive preview, explore a sample project in Dojo, or install BuildNinja and connect one of your own repositories.