The core production builds are healthy. The problem is not build delivery; it is a persistently failing unit-test lane that creates noise, burns roughly an hour per attempt, and hides useful signal.
John Deere Quest builds, Pico builds, Windows builds, ForgeFX build scripts, and JDMini builds all reported 100% success in the sampled window.
QuestUnitTests_JohnDeereUnitTests failed 58 of 59 runs. That single lane accounts for about 95% of all TeamCity failures.
Median queue time was 0 minutes; p90 queue was 14.5 minutes. The pain is runtime and test failure, not capacity starvation.
| Build type | Total | Success | Failures | Median | P90 | Read |
|---|---|---|---|---|---|---|
| John Deere Version Updates BuildTrigger_JohnDeereVersionUpdates | 61 | 98.4% | 1 | 1.5m | 2.3m | Needs attention |
| John Deere Unit Tests QuestUnitTests_JohnDeereUnitTests | 59 | 1.7% | 58 | 68.3m | 86.6m | Needs attention |
| John Deere Builds QuestBuilds_JohnDeereBuilds | 55 | 100% | 0 | 48.2m | 101.5m | Healthy |
| Build Scripts ForgeFX_BuildScripts | 31 | 100% | 0 | 0.9m | 0.9m | Healthy |
| Pico John Deere Builds QuestBuilds_PicoJohnDeereBuilds | 11 | 100% | 0 | 41m | 72m | Healthy |
| John Deere Windows Builds WindowsBuilds_JohnDeereWindowsBuilds | 2 | 100% | 0 | 46.8m | 47.5m | Healthy |
| ForgeSim Unit tests QuestUnitTests_ForgeSimUnitTests | 2 | 0% | 2 | 10.5m | 12.1m | Needs attention |
| Jdmini Builds Workbench_JdminiBuilds | 1 | 100% | 0 | 8m | 8m | Healthy |
| Lane | Failure count | Recent failure text | Latest source |
|---|---|---|---|
| John Deere Unit Tests QuestUnitTests_JohnDeereUnitTests | 58 | Tests failed: 4, passed: 109, ignored: 4 | TeamCity #706 |
| ForgeSim Unit tests QuestUnitTests_ForgeSimUnitTests | 2 | Tests failed: 5, passed: 10, ignored: 7 | TeamCity #172 |
| John Deere Version Updates BuildTrigger_JohnDeereVersionUpdates | 1 | Build stopped: Updates were rejected because the remote contains work that you do not have locally. (new); exit code 1 (Step: GIT> Commit/Push === Version === (Command Line)) (new) | TeamCity #687 |
ForgeBuild is a separate wallboard for the forgeapps monorepo. It does not replace John Deere Unity/TeamCity history, but it confirms whether ForgeFX web app deployment plumbing is currently broken or drifting.
The strict green score requires GitHub, Vercel metadata, live URL, DNS, and drift all to be clean. The report found 0 broken apps and 0 drifting apps, but many apps lack recent/complete Vercel deploy metadata, so they are not counted as fully green even when their live sites return 200 and DNS resolves.
| App | GitHub | Vercel | Live | DNS | Drift |
|---|---|---|---|---|---|
| adamkane | committed | no recent deploy | 200 OK | resolves | unknown |
| adamobot | committed | unknown | 200 OK | resolves | in sync |
| ally | committed | no recent deploy | 200 OK | resolves | unknown |
| ara | committed | no recent deploy | 200 OK | resolves | unknown |
| bofa | committed | no recent deploy | 200 OK | resolves | unknown |
| chetan | committed | unknown | 200 OK | resolves | in sync |
| deepwiki | committed | no recent deploy | 200 OK | resolves | unknown |
| dopples | committed | unknown | 200 OK | resolves | in sync |
| example | committed | unknown | 200 OK | resolves | in sync |
| fitfinder | committed | no recent deploy | 200 OK | resolves | unknown |
| forgebase | committed | unknown | 200 OK | resolves | in sync |
| forgeboard | committed | unknown | 200 OK | resolves | in sync |
| forgebooks | committed | unknown | 200 OK | resolves | in sync |
| forgebot | committed | no recent deploy | 200 OK | resolves | unknown |
| forgebrief | committed | no recent deploy | 200 OK | resolves | unknown |
| forgebuild | committed | no recent deploy | 200 OK | resolves | unknown |
Pull the last 10 failing logs for QuestUnitTests_JohnDeereUnitTests, cluster stack traces, and assign one owner-ready bug around the destroyed Canvas / boot-screen transition failure.
Until the unit-test cluster is fixed, mark the known failure pattern separately so green Quest builds stay visible.
Finish Vercel project mapping for apps reporting unknown/no recent deploy so the wallboard becomes stricter and less ambiguous.