Skip to main content

Release Notes: Version 1.2.0

This release of BuildNinja significantly enhances Git visibility, Git-driven automation, trigger observability, and AI-assisted build intelligence. Version 1.2.0 introduces a dedicated Git Changes view with visual commit graphs, lightweight Git previews in Build History, a redesigned Git Trigger system, enhanced Run Build controls, advanced trigger error tracking, and expanded AI-powered analysis with a global AI side panel.

Released: 01 June 2026

Docker Images:

  • grapehub/buildninja-server:1.2.0
  • grapehub/buildninja-agent:1.2.0

What's New​

  • Added a Git Changes tab in Build Details with visual commit graphs and multi-VCS support.
  • Enhanced Build History with commit counts, recent commits, and branch previews.
  • Introduced Git Trigger to automatically trigger builds based on Git activity.
  • Revamped Trigger configuration UI to support multiple trigger types.
  • Enhanced Run Build modal with branch selection and commit-level execution.
  • Added Trigger failure notifications and detailed logs.
  • Introduced AI Build Analysis reports with risk assessment and code-level insights.
  • Added a Global AI Side Panel for context-aware assistance across the application.
  • Introduced AI Runner for executing AI-powered analysis steps within build workflows.
  • Added AI-powered log analysis and configuration explanations.

Features​

  • Git Changes Visualization: A new Git Changes tab in Build Details provides a detailed view of commits between builds, including an SVG-based commit graph, commit metadata, author tooltips, copyable commit IDs, and support for multiple VCS repositories. See Build Result TabsProjects and Builds help you organize your work and run builds in BuildNinja. Projects group related applications and settings, while Builds define how your code is compiled, tested, and packaged..
  • Build History Git Preview: Build History now displays commit counts per build with a dropdown showing recent commits and associated branches. A “Show more” action allows quick navigation to the full Git Changes view. See Build TabsProjects and Builds help you organize your work and run builds in BuildNinja. Projects group related applications and settings, while Builds define how your code is compiled, tested, and packaged..
  • Git Trigger: Automatically triggers builds on Git events such as pushes and merges. Supports branch patterns, commit type filtering, commit message patterns, polling intervals, allowed author filters, and custom VCS configuration. See Git TriggerBuildNinja supports Build Triggers that allow builds to start automatically based on time schedules or Git activity. These triggers help streamline workflows by eliminating the need for manual build execution..
  • Trigger UI Redesign: The trigger Add/Edit modal has been redesigned with global trigger settings, context-based runtime inputs, and advanced Git Trigger options. Trigger cards and the Triggers Dashboard now clearly reflect trigger types and Git-specific details. See Configure Build TriggersBuildNinja supports Build Triggers that allow builds to start automatically based on time schedules or Git activity. These triggers help streamline workflows by eliminating the need for manual build execution..
  • Run Build Enhancements: The Run Build modal now supports selecting VCS branches or running builds against a specific commit ID. Commit IDs override branch selection, enabling precise, reproducible builds across multiple repositories. See Run BuildsRunning a build is the core action in your CI/CD process. It initiates a predefined sequence of steps such as compiling code, running tests, validating artifacts, and preparing outputs for deployment..
  • Trigger Logs & Error Handling: Newly failed triggers are surfaced through navigation badges and dashboard highlights. A dedicated Trigger Logs modal displays the last 15 trigger runs with status, timestamps, messages, and log download support. See View Trigger Logs and ErrorsBuildNinja supports Build Triggers that allow builds to start automatically based on time schedules or Git activity. These triggers help streamline workflows by eliminating the need for manual build execution..
  • AI Runner: A dedicated runner that enables execution of AI-powered analysis tasks as part of build workflows. The AI Runner supports log analysis, configuration inspection, and code-difference evaluation, and integrates seamlessly with existing build configurations. See AI RunnerThe AI Runner performs AI-driven analysis on repository code changes (diffs) associated with a specific build. It evaluates what has changed between revisions to assess potential build risk and generate the AI Build Anal….
  • AI Build Analysis: A document-style AI Analysis report is available in Build Details, providing failure risk assessment, severity-based issue filtering, file-level insights, code comparisons, and actionable fix recommendations. See AI Build Analysis ReportAI Build Analysis Report is a document-style report integrated into the Build Results in AI Analysis tab. It provides automated build risk assessment along with detailed file-level and code-level insights for completed b….
  • AI Global Side Panel: A persistent AI assistant accessible throughout the BuildNinja interface via a floating handle or keyboard shortcut. The panel delivers context-aware actions, supports follow-up questions, tracks session history, allows model tier selection, and provides real-time analysis feedback. See BuildNinja AI Side PanelBuildNinja AI Side Panel is a persistent, global AI assistant available throughout the BuildNinja application. It provides real-time, context-aware support to help users analyze builds, understand configurations, and inv….
  • Specialized AI Modules: Includes AI-powered log analysis for root cause identification and configuration explanation views for detailed breakdowns of build settings and behavior. See Specialized Analysis ModulesSpecialized Analysis Modules provide focused, AI-powered insights for specific build artifacts, helping teams diagnose failures and understand complex build behavior without manually inspecting logs or configuration file….

Installation​

# Download the Docker image.
docker pull grapehub/buildninja-server:1.2.0

# Run the container from the downloaded image.
docker run -d -p 8080:8080 --name buildninja grapehub/buildninja-server:1.2.0

Licensing​

Licensing for BuildNinja is governed by the official BuildNinja Licensing PolicyBuildNinja offers full access to all platform features for all users. However, build execution, services, and entitlements vary based on the user’s licensing and evaluation status.. Please review the policy for details on license types and usage limitations.

Feedback​

Report any issues at hello@grapehub.io.