feat(ci): verify real service startup with an isolated panel fixture - #40
Merged
Merged
Conversation
Signed-off-by: edbfi <326875205+edbfi@users.noreply.github.com>
7 tasks
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.
The current smoke only exercises
--help, leaving service initialization untested. This adds a mandatory Linux job that builds the real Wings executable, creates a disposable internal Docker network and local panel fixture, then verifies authenticated system/server responses, rejected unauthenticated access, SFTP readiness and panel reset.The same harness supplies malformed panel data and requires startup to fail before readiness. Configuration, ports, state and credentials are ephemeral; teardown stops the service and removes the network. This covers rootless service initialization with no game servers; VPN/game-container behavior remains a separate acceptance item.
Validation: Python syntax, workflow actionlint with the repository's current runner-label configuration, and diff checks passed locally. Full Docker execution is delegated to the required hosted Linux job because the development host has no Docker runtime. Existing quality, platform and CodeQL checks remain mandatory.