Skip to main content

Glossary

A collection of technical terms and their definitions.

A

Access Level
The permission level assigned to a user for a project or build configuration, selected from a dropdown when adding or managing members.
Related terms: Editor, Manager
Agents
The BuildNinja interface for managing agents that execute builds and report build status.
Agents Criteria
A tab in a build configuration where you define rules used to select suitable build agents for execution, based on agent properties and capabilities.
Related terms: BuildNinja Agent
AI Analysis
A tab within Build Results that surfaces the AI Build Analysis Report, providing automated risk assessment and code-level insights for a completed build.
Related terms: Build Results, AI Runner
AI Build Analysis Report
A document-style report integrated into the AI Analysis tab of Build Results, providing automated build risk assessment along with file-level and code-level insights.
AI Runner
A build runner that performs AI-driven analysis on repository code changes (diffs) associated with a build, evaluating what changed to assess risk and generate insights.
Related terms: Runner, runner_ai
Analyze Logs
An AI-powered feature that analyzes build execution logs, highlighting errors, tracing their origin, and grouping related issues to help diagnose failures.
Related terms: Execution Logs, KenzoAI
App Key
The application key generated in the KenzoAI Developer Portal, used together with the App Secret to authenticate BuildNinja's integration with KenzoAI services.
Related terms: App Secret, KenzoAI
App Secret
The application secret generated in the KenzoAI Developer Portal, used together with the App Key to authenticate BuildNinja's integration with KenzoAI services.
Related terms: App Key, KenzoAI
args
A YAML field containing runner-specific arguments required for a build step's execution.
Related terms: argsProtected, build-steps
argsProtected
A YAML field that securely stores sensitive argument values, keeping them out of plaintext build logs.
Related terms: args, Protected
Artifact Conditions
The Condition field determines when artifacts are collected after a build: Always (regardless of the build result), Only if build succeeds, or Only if build fails.
Related terms: Artifacts
Artifacts
Build outputs, such as compiled binaries, packages, or bundles, that BuildNinja retains after a build completes so they can be downloaded, reviewed, or shared.
Related terms: Build Configuration
Authentication Mode
The method used to authenticate with a version control repository when configuring a VCS connection.
Related terms: VCS Settings

B

Build Configuration
A configuration that defines how a build is executed, including its execution steps, build parameters, triggers, agent criteria, artifacts, and other build settings.
Related terms: Projects, Execution Steps
Build Number
A unique identifier assigned to each build execution, used to locate and reference specific build results.
Build Parameters
Configurable values that define build behavior. Parameters can store configuration settings, runtime inputs, or sensitive credentials and are available to build steps during execution.
Build Results
The output of a completed build, including logs, artifacts, Git changes, and AI analysis, organized into tabs such as Overview, Artifacts, Execution Logs, Git Changes, and AI Analysis.
Build Triggers
Defined conditions, scheduled or based on VCS events, under which a build is automatically started, managed from the Triggers tab or Triggers Dashboard.
Related terms: Triggers, Git Trigger
build-steps
A YAML configuration section that specifies the build execution steps, including runners, commands, and parameters, executed in the order they appear.
BuildNinja Agent
A machine (physical, virtual, or containerized) registered with the BuildNinja Server that executes assigned build jobs and reports results back.
BuildNinja AI
The suite of AI-powered features in BuildNinja that helps teams analyze build logs, explain configurations, investigate build failures, and gain actionable insights throughout the build lifecycle using KenzoAI.
BuildNinja AI Side Panel
A persistent, global AI assistant available throughout the BuildNinja application, providing real-time, context-aware analysis and support for builds and configurations.
Related terms: KenzoAI, Model Tier
BuildNinja Server
The central component of a BuildNinja deployment that hosts the web interface, manages projects and builds, and coordinates work distributed to Agents.
Related terms: BuildNinja Agent

C

Cache
A VCS setting that controls whether cloned repositories and dependencies are reused across builds to speed up execution.
Related terms: VCS Settings
Checkout Directory
An optional VCS setting specifying the directory into which the repository is checked out; defaults to a recommended location if left blank.
Related terms: VCS Settings
CI/CD (Continuous Integration and Continuous Delivery/Deployment)
The practice of automatically building, testing, and delivering software to enable faster, more reliable software releases.
Client ID
The public identifier issued by an identity provider when registering an OAuth application, used together with the Client Secret for SSO integration with BuildNinja.
Client Secret
The confidential secret issued by an identity provider alongside the Client ID, used to authenticate an OAuth application for SSO integration with BuildNinja.
Command Line Runner
A runner that executes one or more shell or batch commands directly on a BuildNinja Agent, typically for running command-line tools, scripts, and automation tasks.
Related terms: Runner, runner_cmd
Config File Runner
A runner that executes builds using a YAML configuration file, enabling build logic to be version-controlled, reviewed, and reused across projects and environments.
Containerized BuildNinja Architecture
A deployment approach where the BuildNinja Server and Agent run as Docker containers or on Kubernetes, simplifying installation and enabling fully containerized environments.
Continuous Delivery
A software development practice that extends Continuous Integration by automatically preparing validated code changes for release after they pass automated testing.
Continuous Deployment
A software development practice that extends Continuous Delivery by automatically deploying validated code changes to production without manual approval.
Continuous Integration
A software development practice in which code changes are frequently merged into a shared repository and automatically built and tested to detect issues early.
Custom YAML Configuration Files
User-defined YAML files that describe build steps and requirements, executed via the Config File runner in addition to exported configurations.

D

Dashboard
The BuildNinja interface that provides a centralized, real-time overview of build activity, system status, recent builds, and key metrics.
Docker
An open-source platform that enables building, packaging, and deploying applications using lightweight, portable containers; BuildNinja can build and push Docker images as part of CI.
docker-compose.yml
A YAML configuration file used by Docker Compose to define and manage multi-container applications, commonly used for local development and BuildNinja Server/Agent deployment.
Related terms: Docker

E

Editor
A project- or build-level role that can modify VCS settings, execution steps, parameters, and artifacts, but cannot manage triggers or user access.
Related terms: Manager, Access Level
Execute Next Command
A Command Line Runner setting that specifies whether execution continues with the next command in a step if the previous command fails.
Execution Logs
A tab within Build Results showing the raw output produced during a build's execution, used for troubleshooting and AI-driven log analysis.
Related terms: Build Results, Analyze Logs
Execution Steps
The ordered sequence of steps that a build configuration executes, with each step using a specific runner to perform a build task.
Related terms: Runner, Build Configuration
Executor
A project- or build-level role that can trigger builds and view build results, but cannot modify VCS settings, execution steps, parameters, or artifacts.
Related terms: Editor, Manager, Viewer, Access Level
Explain Config
An AI-powered feature that analyzes a build configuration and explains the purpose and impact of its settings in plain language.
Related terms: KenzoAI
Expose on Env
A build parameter option that makes the parameter available to all build steps as a standard OS environment variable.

G

Git Changes
A Build Results tab that displays the Git changes between the current build and the previous commit across supported VCS repositories. It includes commit history and a visual commit graph for each repository.
Git Trigger
A trigger type that automatically starts a build when Git events occur, including pushes, merges, or all supported Git events.
Related terms: Build Triggers, Triggers

H

History
A tab in a build configuration showing past build executions, including trigger details, duration, commits, and branch information.

K

KenzoAI
The AI platform integrated with BuildNinja to power AI features such as the AI Side Panel, AI Build Analysis Report, Log Analysis, and Explain Config.
kubeconfig
A configuration file containing credentials and connection details needed to access a Kubernetes cluster, required by a BuildNinja Agent to run Kubernetes-related build steps.
Related terms: Kubernetes, kubectl
kubectl
The command-line tool for interacting with a Kubernetes cluster; must be installed and available on a BuildNinja Agent to execute Kubernetes-related build steps.
Related terms: Kubernetes, kubeconfig
Kubernetes (K8s)
An open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. BuildNinja can deploy applications to Kubernetes clusters as part of a CI/CD pipeline.
Related terms: kubectl, kubeconfig

L

License Key
A unique code used to activate a BuildNinja license. License keys are available under My Licenses after purchase.

M

Mail Templates
Predefined templates that define the subject and body of email notifications BuildNinja sends for events such as user registration, password resets, and build status changes.
Related terms: Notifier Settings, Settings
Manager
A project- or build-level role that includes all Editor permissions and can manage triggers and user access.
Related terms: Editor, Access Level
Model Tier
A BuildNinja AI setting that determines the AI capability tier used across AI-powered features. Available tiers include Economy, Optimized, and Best.
Related terms: KenzoAI, AI Runner
MSBuild Runner
A runner that builds .NET projects and Visual Studio solution files using the Microsoft Build Engine (MSBuild).
Related terms: Runner, runner_msbuild

N

Native Git support
A build execution approach where Git operations (cloning, fetching, checkout, pulling, submodules, authentication) run directly through the Git binary installed on the build agent, rather than through plugins, wrappers, or proxy-based integrations.
Nodes
The physical or virtual machines that run pods in a Kubernetes cluster; a cluster consists of control plane nodes that manage the cluster and worker nodes that run containerized workloads.
Related terms: Kubernetes, kubectl
Notification Settings
Build-configuration-level settings that determine when and to whom BuildNinja sends email notifications about build events.
Notifier Settings
System-level settings that configure the global SMTP integration BuildNinja uses to send notifications across all projects.

O

Overview
A Build Results tab that displays key information about a completed build, including trigger details, build duration, agent information, and a summary of executed build steps with their status, execution time, and warnings.

P

Passphrase
The passphrase associated with an SSH private key, required if the key is encrypted, when using SSH Runner authentication.
Related terms: SSH Runner, SSH Key
Pending Approvals Tab
The default tab in the Users section showing incoming user registration requests awaiting administrator review.
Related terms: Users, Users Tab
Profile
The BuildNinja interface that provides access to user profile information and account settings.
Projects
A top-level organizational unit in BuildNinja that groups related build configurations and settings for an application.
Related terms: Build Configuration
Prompt on Run
A build parameter option that prompts the user to provide a value when a build is manually triggered, rather than using a stored default.
Related terms: Build Parameters
Protected
A build parameter option that encrypts and masks a sensitive value in the UI and logs. Protected values cannot be retrieved in plaintext after creation.

Q

Queue
The BuildNinja interface that displays builds waiting to be executed and provides visibility into their scheduling and execution order.

R

Redirect URI
The callback URL configured in an identity provider's OAuth application settings, which must match your BuildNinja instance for SSO to work correctly.
Root Password
The password of a remote machine's root user, used for privileged SSH Runner authentication when required.
Related terms: SSH Runner, Passphrase
Run Build
The action of manually starting a build configuration's execution, which enters the build into the execution queue.
Related terms: Queue
Runner
The component within an execution step that determines how a build step is carried out, such as Command Line, MSBuild, SSH, Script, AI, Config File, or VSTest.
runner_ai
The YAML runner key used to invoke the AI Runner in a Custom YAML Configuration File.
Related terms: AI Runner
runner_cmd
The YAML runner key used to invoke the Command Line Runner in a Custom YAML Configuration File.
Related terms: Command Line Runner
runner_configfile
The YAML runner key used to invoke the Config File runner in a Custom YAML Configuration File.
Related terms: Config File Runner
runner_msbuild
The YAML runner key used to invoke the MSBuild Runner in a Custom YAML Configuration File.
Related terms: MSBuild Runner
runner_script
The YAML runner key used to invoke the Script Runner in a Custom YAML Configuration File.
Related terms: Script Runner
runner_ssh
The YAML runner key used to invoke the SSH Runner in a Custom YAML Configuration File.
Related terms: SSH Runner
runner_vstest
The YAML runner key used to invoke the VSTest Runner in a Custom YAML Configuration File.
Related terms: VSTest Runner

S

Scheduled Trigger
A trigger type that automatically starts a build at a specified time or on a recurring schedule.
Script Runner
A build runner that executes multi-line scripts using a selected shell, supporting complex logic, conditionals, and loops.
Related terms: Runner, runner_script
Server URL
The network address of a BuildNinja Server that a BuildNinja Agent uses to establish a connection. It is configured during Agent installation.
Settings
The BuildNinja interface for configuring system-wide settings and platform behavior.
Specialized Analysis Modules
A collection of AI-powered features, including Analyze Logs and Explain Config, that help diagnose build failures and explain build configurations.
SSH Key
A custom SSH private key used to authenticate with a remote host when using the SSH Runner's Custom SSH Key authentication option.
Related terms: SSH Runner, Passphrase
SSH Runner
A build runner that executes commands on a remote machine over SSH, used for remote deployments and post-build automation.
Related terms: Runner, runner_ssh, SSH Key
SSO (Single Sign-On)
An authentication mechanism that allows users to sign in once and securely access multiple connected applications without re-entering credentials. BuildNinja supports SSO through OAuth 2.0 with supported identity providers.
SSO Settings
The administrator settings section for configuring SSO identity providers and centralized user authentication.
Related terms: Settings
Success Exit Code
A build step setting specifying which command exit code should be treated as successful execution (default 0).
System Admin
A user role with permission to manage users, licensing, and system-wide settings across a BuildNinja instance.

T

Triggers
The BuildNinja interface for configuring and managing conditions that automatically start builds.
Related terms: Build Triggers, Git Trigger

U

Users
The BuildNinja interface for managing user accounts, roles, and access permissions.
Users Tab
The BuildNinja interface for managing user accounts, roles, permissions, and account status across the platform.

V

VCS (Version Control System)
A source code management system, such as Git, that BuildNinja connects to for retrieving source code during a build.
Related terms: VCS Settings
VCS Settings
The section of a build configuration where the Version Control System (VCS) connection, including the repository, branch, and authentication settings, is configured.
Viewer
A project- or build-level role that can view builds, build history, settings, and artifacts, and download artifacts, but cannot trigger builds or modify project settings or configurations.
VSTest Runner
A build runner that executes automated tests built with Visual Studio test frameworks and generates structured test reports.
Related terms: Runner, runner_vstest

W

Working Directory
The directory from which a build step's commands are executed on the build agent; defaults to the repository checkout directory if not specified.

Total terms: 101

Ask AI about BuildNinja

ChatGPTClaudePerplexityGeminiGrok