After building the binary we perform a minimally viable invocation (e.g. seafowl --version) using each OS in the matrix. Serves as a basic smoke test to answer the Q "did it run?"
In case of non-zero exit code, pass it into the exit call. I've only observed macOS so far, which today returned 134 for the binary with the SSL issue.
How do we know it works?
Because I don't have a Windows machine immediately available to test on, I can't say for 100% sure. π
My understanding is that because bash is running across all three OSes, we can at least say the bash script ran because act -n on my dev server returned
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β git clone 'https://github.com/docker/build-push-action' # ref=v3
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β git clone 'https://github.com/actions/upload-artifact' # ref=v3
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] π§ͺ Matrix: map[build:linux os:ubuntu-18.04 target:x86_64-unknown-linux-gnu]
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Install prerequisites
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Install prerequisites
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Checkout the repository
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Checkout the repository
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main rustup toolchain install stable --profile minimal
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main rustup toolchain install stable --profile minimal
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Swatinem/rust-cache@v2
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Swatinem/rust-cache@v2
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Build the release binary
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Build the release binary
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Strip release binary (linux and macos)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Strip release binary (linux and macos)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Test invoking the binaries
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Test invoking the binaries
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Prepare artifact name
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Prepare artifact name
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Login to DockerHub (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Login to DockerHub (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Determine Docker tags
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Determine Docker tags
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Build and push Docker image (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Build and push Docker image (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Main Upload binaries as artifacts
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Main Upload binaries as artifacts
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Post Build and push Docker image (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Post Build and push Docker image (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Post Login to DockerHub (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Post Login to DockerHub (Linux only)
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Run Post Swatinem/rust-cache@v2
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] β Success - Post Swatinem/rust-cache@v2
*DRYRUN* [Build nightly binaries and perform releases/Build the binaries-1] π Job succeeded
And we see success for the new step, "Test invoking the binaries."
Goal
Help reduce the risk of building a bad binary
Method
seafowl --version
) using each OS in the matrix. Serves as a basic smoke test to answer the Q "did it run?"exit
call. I've only observed macOS so far, which today returned134
for the binary with the SSL issue.How do we know it works?
Because I don't have a Windows machine immediately available to test on, I can't say for 100% sure. π My understanding is that because bash is running across all three OSes, we can at least say the bash script ran because
act -n
on my dev server returnedAnd we see success for the new step, "Test invoking the binaries."
Feedback welcome.