- The problemBuilds were limited to three TeamCity agents, and every extra agent had to be bought.
- The moveIn May 2026 the team set up its own BuildNinja server with six agents on Windows and Linux.
- The result57 Android builds so far, about 10 minutes each, with no cost per agent.
“Your Binoculars” is an app for learning English, available on the web and on Android. It is built by a product team at GrapeCity India, the company that also makes BuildNinja. The team works independently: it runs its own server and configured it without our involvement.
Before and after
The team builds an Android app, a website and six backend services. One app build keeps an agent busy for about ten minutes, so with three agents other builds had to wait.
| Topic | On TeamCity | On BuildNinja |
|---|---|---|
| Build agents | agent agent agent | WIN WIN WIN WIN LINUX LINUX |
| Adding an agent | A purchase | Install it |
| Cost per agent | Paid beyond three | None |
“We had three agents on TeamCity. If we wanted a fourth we had to buy it, so we made do with three.”
What mattered beyond cost
Full control of the infrastructure
The server and all six agents run on the team’s own machines, inside its own network.
No pipeline language to learn
The steps are the same PowerShell and Flutter commands the team already used. Nothing was rewritten.
Windows and Linux together
One server distributes work to both kinds of agent, so the app and the services share one setup.
A short path to the first build
BuildNinja’s documentation puts installation at about five minutes and a first build at about fifteen.
“Here I installed the agents we needed. Nobody had to approve anything.”
Inside the Android build
The app is written in Flutter. A team member starts a build whenever there are changes to test, typically every week or two.
- 1
Prepare
A PowerShell step brings the app code and its configuration, kept in two repositories, into one folder.
- 2
Build
Flutter produces an APK and an app bundle, versioned from BuildNinja’s build counter.
- 3
Store
When the build succeeds, both files are kept as build artifacts.
# the build step, as configured
flutter build appbundle --flavor dev \
--build-name=1.0.%BN_BUILD_COUNTER%-dev \
--build-number=%BN_BUILD_COUNTER%Across 57 builds the average is 10 minutes 16 seconds, and the ten most recent builds all completed successfully.
Finding the root cause of a failed build
Three of the 57 builds have failed. In build 46, the last lines of the log said only that the build had failed. The reason was fifteen lines earlier, among unrelated warnings.
FAILURE: Build failed with an exception. Execution failed for task ':app:compileFlutterBuildDevRelease'. BUILD FAILED in 2m 50s
lib/main.dart:13:1: Error: Directives must appear before any declarations.
This is the problem Build Intelligence, the AI built into BuildNinja, is designed to solve. Its log analysis:
- Reads the entire build log, not just the last error
- Summarises what happened in plain language
- Ranks findings by severity, with the root cause first
- Suggests a fix, and continues in AI chat with the build’s context
flutter pub get completed. The build failed in the Build App Bundle step while compiling the Dart code for the dev release: an import directive in lib/main.dart appears after a declaration. Gradle then reported the failed task and stopped. No artifacts were published.Import directive placed after a declaration in main.dart CRITICAL
lib/main.dart:13:1 Directives must appear before any declarations. Move the import to the top of the file with the other imports. This is the cause of the failed task :app:compileFlutterBuildDevRelease.
242 untranslated messages in the Hindi locale WARNING
Localization generation reported 242 untranslated messages for hi. This did not cause the failure, but those strings will fall back to English.
A newer Flutter version is available WARNING
The agent builds with Flutter 3.44.2 through FVM. The tool reported that a newer version exists. Not related to this failure.
Also on the server: the six backend services and the website each have their own build configuration. These have run once each so far; the Android build accounts for the team’s regular activity.