Skip to main content

Release Notes: Version 1.2.0

This release of BuildNinja significantly enhances Git visibility, Git-driven automation, and trigger observability. Version 1.2.0 introduces a dedicated Git Changes view with visual commit graphs, lightweight Git previews in Build History, a redesigned Trigger system, enhanced Run Build controls, and advanced trigger error tracking to improve transparency, automation, and reliability across build workflows.

Released: 15 August 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.

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..

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 flexible licensing options for evaluation, small teams, and enterprise deployments. Your license determines the available platform limits, build capacity, and included entitlements.. Please review the policy for details on license types and usage limitations.

Feedback​

Report any issues at buildninja@grapecity.global.