Migrate and expand Semaphore integration test suite - #4
Merged
Conversation
This was referenced Sep 4, 2026
Open
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
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
SemaphoreShellOutputFixturesexternalTesttask for user-managed Semaphore installationsThe repositories share commit
531b7c0, so this PR uses a regular Git merge rather than copying the current tree. The official repository's seven unique commits and the legacy suite's thirteen unique commits remain reachable in history.Validation
./gradlew --no-daemon qualityGate— passedscripts/run-external-tests.sh --no-daemonagainst a local Semaphore stand — 2 passedv2.19.7 -> v2.19.8seed and verify phases passedv2.19.7 -> v2.19.8seed and verify phases passedGitHub Actions evidence
Known product failure
The pinned stable release images can lose short or early task stdout. This directly fails
ShellOutputTestand can also hide output markers used by task-stop, Git, and SSH diagnostic assertions. The affected reports consistently show a successful task/fixture setup with stdout missing from the API response; configuration startup, authentication, database, runner, OIDC, Git HTTPS, TOTP, and encryption flows are otherwise healthy.The product fix was merged in semaphoreui/semaphore#4159, but it is not included in the latest stable release (
v2.19.12). The publishedsemaphoreui/semaphore:developimage is currently an old2-16-stablebuild, so it cannot be used as a reliable replacement. The regression assertions are intentionally not disabled or weakened.Existing PRs