fix: discard the build record git:sync starts when nothing is built
cmd-git-sync calls dokku_setup_build_capture before the clone/fetch, because it cannot know whether there is anything to deploy until it has fetched. Both paths that then decline to build - a plain `git:sync` with no build flag, and a `--build-if-changes` poll that finds the remote unchanged - returned without ever finalizing that record. The record stayed at status=running forever, which has three consequences on an app polled on a timer: - PruneAppBuilds only runs from builds-record-finalize, so nothing prunes the ticks while the app is idle; they accumulate without bound, invisibly, because builds:list caps output at the retention count. - The next real deploy's ReapAbandonedBuilds finalizes each of them as status=failed, exit_code=-1, with finished_at stamped at the moment of reaping - indistinguishable on disk from a build that really failed, and with a duration that grew to the polling interval. - That same deploy's prune then keeps the newest records by started_at, which after an idle stretch are the ticks, deleting the last real deploy's record and log. Add a builds-record-discard trigger that removes a non-terminal record and its log, and call it from both no-op paths in cmd-git-sync. The trigger leaves missing and already-terminal records alone, so it can never delete real history. Fixes #9030 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
aa39920cc7
commit
dc27668e09
10 files changed
+188
-1
No files matched your search
@@ -19,6 +19,10 @@ func main() {
|
||||
switch trigger {
|
||||
case "builds-generate-id":
|
||||
err = builds.TriggerBuildsGenerateID()
|
||||
case "builds-record-discard":
|
||||
appName := flag.Arg(0)
|
||||
buildID := flag.Arg(1)
|
||||
err = builds.TriggerBuildsRecordDiscard(appName, buildID)
|
||||
case "builds-record-finalize":
|
||||
appName := flag.Arg(0)
|
||||
buildID := flag.Arg(1)
|
||||
|
||||
Reference in new issue
Block a user