Nightly builds: publish Darling service + viewer + pg-runtime zip - #1550
Merged
Conversation
The nightly release carried only Dashboard/Lite/Installer, so testing Darling in another environment meant building from dev. Mirror the release workflow's Darling artifact into the nightly job: - restore + publish DarlingService and DarlingViewer (locked-mode) - pg-runtime cache + fetch with the SAME content-hash key build.yml uses, so the ~340MB EDB/TimescaleDB fetch runs at most once per pin-set and nightly/release share the assembled zip - package PerformanceMonitorDarling-<version>.zip in the release layout: service at root (darling.sample.json alongside), viewer under viewer\, pg-runtime.zip beside the service exe where DarlingManagedPostgres extracts it on first run - the zip flows into SHA256SUMS.txt and the nightly release via the existing releases/*.zip glob; unsigned like every nightly artifact Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
PerformanceMonitor.Darling.Service has no packages.lock.json, so a --locked-mode restore fails with NU1004. build.yml never restores it directly either — the release path's dotnet publish does the implicit restore. Mirror that: locked restore for the viewer only (which has a lock file), publish handles the service. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
pull Bot
pushed a commit
to ehtick/PerformanceMonitor
that referenced
this pull request
Jul 29, 2026
…hat executes Scheduled workflows always execute the DEFAULT branch's copy of the workflow file, while nightly artifacts deliberately build from dev's tree. That skew is exactly how the 2026-07-26 scheduled nightly failed (run 30194606068): main's stale copy still read Dashboard/Dashboard.csproj, a path erikdarlingdata#1612 moved to deprecated/ on dev, so 'Set nightly version' died on a file missing from the tree it had just checked out. Same trap as before (erikdarlingdata#1550/erikdarlingdata#1551) - syncing the file again would fix tonight and re-break at the next pre-release layout drift. Structural fix instead: on schedule the workflow does nothing but re-dispatch itself onto the dev ref (GITHUB_TOKEN can create workflow_dispatch runs; the Actions recursion guard exempts workflow_dispatch, and the dispatched run cannot loop back because it arrives as workflow_dispatch, not schedule). A workflow_dispatch run executes the DISPATCHED ref's copy of the file - dev's, current by definition - so after a one-time sync of this file to main, main's copy has exactly one tree-independent job that must keep working, and nightly logic changes take effect the night they merge to dev. Semantics preserved: manual dispatches (from_schedule defaults false) always build, exactly as before; the scheduled path keeps the 24h new-commit check via from_schedule=true; the artifact-publishing build job stays pinned to ref dev so a branch dispatch still cannot ship branch binaries. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The nightly release carried only Dashboard, Lite, and the CLI Installer — testing Darling in another environment meant cloning and building
dev. This mirrors the release workflow's Darling artifact intonightly.ymlso every nightly publishes a publicPerformanceMonitorDarling-<version>.zip.Changes
DarlingServiceandDarlingViewer(locked-mode restore, same publish commands asbuild.yml)build.ymluses (pg-runtime-<os>-<hash of fetch-pg-runtime.ps1>), so the ~340MB EDB/TimescaleDB fetch runs at most once per pin-set and nightly/release runs share the assembled zip when the cache is visiblebuild.yml"Package Darling (signed)"): service at the archive root withdarling.sample.jsonalongside, viewer underviewer\,pg-runtime.zipbeside the service exe whereDarlingManagedPostgresextracts it on first run — staged frompublish/instead ofsigned/since nightly artifacts are unsigned across the boardSHA256SUMS.txtand the nightly release automatically via the existingreleases/*.zipglob[Unreleased]entry + link-refWhy
Erik needs to stand Darling up on a server in a different environment via an agent. With this, the agent downloads the public nightly zip (stable URL:
https://github.com/erikdarlingdata/PerformanceMonitor/releases/download/nightly/PerformanceMonitorDarling-<version>.zip) instead of needing the repo + SDK to build fromdev.Testing
nightly.ymlparses clean (YAML validated)build.ymlequivalents (publish commands, cache key/path, fetch guard, package layout)workflow_dispatchafter merge — the workflow already supports it)🤖 Generated with Claude Code