Merge pull request #9033 from mvysny/fix/git-sync-build-record-leak

Discard the build record git:sync starts when nothing is built
This commit is contained in:
Jose Diaz-Gonzalez authored and GitHub committed 2026-09-17 17:24:09 -04:00
commit 1ab7095016
10 files changed
+188 -1

No files matched your search

+2
View File
@@ -25,6 +25,8 @@ Every build is identified by a sortable base36 ULID-style id (`DOKKU_BUILD_ID`)
Output is also tagged into syslog as `dokku-<build-id>` so `journalctl -t dokku-<build-id>` continues to work. The on-disk log file is the durable source of truth and is read for `builds:output` even when journald has rotated old entries away.
A run that builds nothing leaves no record behind. `git:sync` has to fetch before it can tell whether there is anything to deploy, so it opens a record up front and discards it again when it turns out there is not - a `git:sync` with no `--build` flag, or a `--build-if-changes` poll that finds the remote unchanged. Without that, an app polled on a timer would accumulate `running` records that are later reaped as spurious failures, pushing real deploys out of the retention window.
### Record schema
```json